Add support for preprocessed messages #650
Open
Conversation
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
1 participant
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.
Overview
In this PR, I add support for preprocessed transactions to the gRPC Yellowstone server, making it a unified API for all Solana data needs. To support preprocessed transactions, we rely on using a Jito shredstream proxy to consume decoded transactions. Alternatively, we could add the filtering capabilities into the shredstream proxy itself. However, it's neater to expose this in the Yellowstone gRPC to keep YS as the fan-out layer.
Next steps:
Testing
Added unit tests for filtering and tested locally that everything works e2e.