feat(core): add Jito sendBundle RPC support#480
Open
Conversation
Add non-standard `sendBundle` RPC endpoint for Jito bundles imitation, allowing clients to submit multiple transactions that are executed sequentially. This is useful for testing applications that use Jito bundles. Key features: - Transactions are processed sequentially in order - Forces skip_preflight to match Jito Block Engine behavior - Returns bundle ID as SHA-256 hash of comma-separated signatures - If any transaction fails, the entire bundle is rejected Note: This is not a 100% bundles implementation as they are not atomic all-or-nothing like real Jito bundles.
Member
Contributor
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.
Summary
sendBundleRPC endpoint for Jito bundles imitationImplementation details
skip_preflight: trueto match Jito Block Engine behaviorNotes
This is not a 100% bundles implementation as they are not atomic all-or-nothing like real Jito bundles. But it's useful for testing apps that want to verify their Jito integration works.
Test plan
cargo test -p surfpool-core jito