sendBundle
Submits a bundled list of signed transactions (base-58 encoded strings) to the cluster for processing. The transactions are atomically processed in order, meaning if any transaction fails, the entire bundle is rejected (all or nothing). This method relays the bundle created by clients to the leader without any modifications. If the bundle is set to expire after the next Jito-Solana leader, this method immediately returns a success response with a bundle_id, indicating the bundle has been received. This does not guarantee the bundle will be processed or land on-chain. To check the bundle status, use getBundleStatuses
with the bundle_id.
A tip is necessary for the bundle to be considered. The tip can be any instruction, top-level or CPI, that transfers SOL to one of the 8 tip accounts. Clients should ensure they have sufficient balance and state assertions allowing the tip to go through conditionally, especially if tipping as a separate transaction. If the tip is too low, the bundle might not be selected during the auction. Use getTipAccounts
to retrieve the tip accounts. Ideally, select one of the accounts at random to reduce contention.
Request
Parameter | Type | Description |
---|---|---|
| array[string] |
|
Request Example
Response
Field | Type | Description |
---|---|---|
| string | A bundle ID, used to identify the bundle. This is the SHA-256 hash of the bundle's transaction signatures. |
Response Example
Last updated