All the uniswapX orders filled by reactorV2(0x00000011F84B9aa48e5f8aA8B9897600006289Be) are not discoverable via API at https://api.uniswap.org/v2/uniswapx/docs
order hash is 0x049577E4C734E5B44F2CB44037EC48140E35AB24D61F8B18A4EF09C4B6AC3888
All orders filled via reactorV1 (0x6000da47483062A0D734Ba3dc7576Ce6A0B645C4) are returned from the API as expected.
Are we simply not returning inactive orders for reactor v2 for some strange reasons ? or it is the case that polling https://api.uniswap.org/v2/uniswapx/ for new open orders is a recipe for missing a large number of the open order ?
linear[bot]
commented
1 week ago
All the uniswapX orders filled by reactorV2(0x00000011F84B9aa48e5f8aA8B9897600006289Be) are not discoverable via API at https://api.uniswap.org/v2/uniswapx/docs
Example: https://etherscan.io/tx/0x205a4d0b8f8fff0647b7e52d1f35f5710d4394efde3365652eb784250df9b5c6
order hash is 0x049577E4C734E5B44F2CB44037EC48140E35AB24D61F8B18A4EF09C4B6AC3888
All orders filled via reactorV1 (0x6000da47483062A0D734Ba3dc7576Ce6A0B645C4) are returned from the API as expected.
Are we simply not returning inactive orders for reactor v2 for some strange reasons ? or it is the case that polling
https://api.uniswap.org/v2/uniswapx/for new open orders is a recipe for missing a large number of the open order ?