sendTransaction RPC Method
Please note that this RPC method requires the Lil' JIT - JITO Bundles and transactions add-on enabled on your QuickNode endpoint. Also, this method serves as a proxy to the Solana sendTransaction RPC method
Please note that Jito no longer provides a minimum tip for bundles. During high-demand periods, the default tip may not suffice to secure a bundle through the auction. To ensure your transaction is properly set up, you must specify a priority fee and a Jito tip. If you set the query parameter bundleOnly=true, the transaction will be sent exclusively as a bundle, bypassing the regular RPC method. Note that this method always sets skip_preflight=true, which means the transaction won't be simulated in the RPC before being sent to the leader, though it will still undergo auction and normal simulations.
Solana Web3.js 2.0 includes the ability to customize RPC methods and transports, allowing you to seamlessly integrate QuickNode Marketplace add-ons into your applications. For more information on how to use QuickNode Marketplace add-ons with Solana Web3.js 2.0, check out these guides: How to Use QuickNode Add-ons using Solana Web3.js 2.0 (Part 1) and How to Use QuickNode Add-ons using Solana Web3.js 2.0 (Part 2)
Parameters
transaction
string
The first transaction signature embedded in the transaction, as base-58 encoded string
object
array
The configuration object with the following fields:
skipPreflight
boolean
If true, skip the preflight transaction checks
preflightCommitment
string
(default: finalized) The commitment level to use for preflight
encoding
string
The encoding format for account data. It can be one of base58 (slow), base64, base64+zstd or jsonParsed
maxRetries
usize
The maximum number of times for the RPC node to retry sending the transaction to the leader. If this parameter is not provided, the RPC node will retry the transaction until it is finalized or until the blockhash expires
minContextSlot
integer
The minimum slot at which the request can be evaluated
Returns
result
string
The First Transaction Signature embedded in the transaction, as base-58 encoded string (transaction id). If sending as a bundle was successful, you can get the bundle_id for further querying from the custom header in the response x-bundle-id
Request
1curl 'https://docs-demo.solana-mainnet.quiknode.pro/' \2--header 'Content-Type: application/json' \3--data '4{5"jsonrpc": "2.0",6"id": 1,7"method": "sendTransaction",8"params": [9"4hXTCkRzt9WyecNzV1XPgCDfGAZzQKNxLXgynz5QDuWWPSAZBZSHptvWRL3BjCvzUXRdKvHL2b7yGrRQcWyaqsaBCncVG7BFggS8w9snUts67BSh3EqKpXLUm5UMHfD7ZBe9GhARjbNQMLJ1QD3Spr6oMTBU6EhdB4RD8CP2xUxr2u3d6fos36PD98XS6oX8TQjLpsMwncs5DAMiD4nNnR8NBfyghGCWvCVifVwvA8B8TJxE1aiyiv2L429BCWfyzAme5sZW8rDb14NeCQHhZbtNqfXhcp2tAnaAT"10]11}12'
Don't have an account yet?
Create your QuickNode endpoint in seconds and start building
Get started for free