Blur order status migration

Recently, we made a change to improve the robustness of our Blur listing aggregation, to ensure we have coverage of 100% of listings, including Blend listings. For most customers, no changes are required. However, for teams that are utilizing the rawData and tracking order status on-chain, you may need to update how your system works. The old system has been fully retired.

In the old system, we provided full Blur order objects, which included the order hash and expiry time. The problem with this method is that it was prone to errors and delays, and did not cover 100% of orders. In the new system, we have 100% coverage of all listings, but we don’t have full order details (hash, expiry, etc). The main difference is that instead of being able to track when orders become invalid yourself (based on expiry or on-chain events), you must rely on our events to know when the status changes (ask.updated websocket or poll the Asks API sorted by updatedAt).

While we agree there are downsides to the new system, we believe that the benefits of 100% coverage and improved robustness are worth it. We recommend all teams migrate ASAP. If you have any questions, feel free to reach out. Remember, only teams that use the rawData are impacted. If you rely on Reservoir to keep track of the status of all orders, no changes are required.

Old Raw Data


New Raw Data

                "price": "0.78",  
                "tokenId": "2625",  
                "createdAt": "2023-05-30T06:18:36.000Z",  
                "collection": "0xecafeba408dd65fdc94030ec5aa99f3bd15c842c"