using opensea api for lists/sales#723
Merged
grantoesterling merged 3 commits intomainfrom Aug 28, 2025
Merged
Conversation
ryley-o
approved these changes
Aug 27, 2025
lindsgil
reviewed
Aug 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switching to the OpenSea Stream API for sale/list events!
There is no contract level filtering on OS end, so it seems the only way is just to receive all sale/list events and manually filter by contract on our side
Sale bot is hooked up to Twitter so it all should work in theory!
Keeping the Reservoir code around in case we need to revert this, but i will open a ticket to remove it all once it is proven stable