Settlement executions API #3290
Closed
Conversation
This file contains 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
squadgazzz
force-pushed
the
settlement-executions-api
branch
from
9cfb30e to
192e627
Compare
MartinquaXD
reviewed
Feb 24, 2025
We need to implement a CI job that combines the data from the DB with the dune query output. The API is the easiest way to fetch it. Otherwise, DB creds can be provided for the CI job. |
|
We decided to go with the DB direct queries. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This is a follow-up to #3289, which adds a way to retrieve the settlement executions based on the auction ids range via the orderbook API. The API remains private to avoid unexpected usage.
How to test
New DB tests. Staging manual test.