Transaction Boost

Wallets and Dapps can seamlessly integrate Blocknative’s Transaction Boost, enabling users to send private transactions to multiple RPC endpoints simultaneously while conveniently monitoring transaction statuses. This integration offers complete customization to adapt to specific preferences.

The table below outlines the supported networks:

Setting up and customizing the endpoint

If no builder or OFA is explicitly defined, Transaction Boost automatically forwards transactions to the following RPC endpoints by default: MEV-Share, MEV-Blocker, MeowRPC,Merkle, Titan,Beaverbuild.org, Builder0x69 ,rsync-builder, Flashbots, Bloxroute , and Blink.

Users can customize the entities that receive their private transactions and program the privacy of their order flow by configuring their RPC URL using the query parameters provided below.

RPC Query Parameters

Checking Transaction Status

You can check the live status of your private transaction by using the Blocknative Explorer or by simply using the following URLs:

  • Mainnet: https://rpc.blocknative.com/boost/tx/YOUR_TX_HASH

After sending the request, you will receive a JSON response in the following format:

{
"txHash":"0x284ff37c96c65579249e11337ccb3f54a4148d98a2638d5a2984e8da6e785478",
"status":"CONFIRMED",
"pendingBlockNumber":9266497, // the pending block where the tx was first received
"maxBlockNumber":9266498, // max block number for the tx to be included, in this example we set it to CURRENT_BLOCK+1
"forwardedTo":[
		{
				"endpoint":"MEV-Blocker",
				"receivedAt":"2023-07-17T15:25:23.218343Z",
				"status":"RECEIVED",
				"endpointMsg":{}
		},
		{
				"endpoint":"Titan",
				"receivedAt":"2023-07-17T15:25:23.218343Z",
				"status":"RECEIVED",
				"endpointMsg":{}
		}
],
"transaction":{
		"from":"0x48bdc4Ed4b6c6a0E32bD2D7075c99eD5F917DDA0",
		"to":"0x99F18940Cb6396FE9233EAFc61D1187Fe86eb43D",
		"gasLimit":21000,
		"maxFeePerGas":1651273110,
		"maxPriorityFeePerGas":1650000000,
		"gasPrice":1650000005,
		"nonce":12,
		"value":20000000
},
"gasUsed":21000,
"blockNumber":9266498,
"builder":"Titan",
"confirmedAt":"2023-07-17T15:25:23.218343Z",
"seenInMempool": false,
"firstSeenInMempool":"", //shows timestamp of when the tx entered mempool (if seen in mempool)
"refund": [{
    "refundRecipient": "0x56C8F2...Bf415a",
    "refundAmount": "10000000", //(in wei)
    "refundTxHash": "0x6a37ff...b8aeb",
}],
"norevert":"true", // is norevert tx
"reorged": false, // set to true if the tx was included in a forked block
"forkedBlockNumber":0, // the forked block number
"forkedBlockHash":"0x..." // the forked block hash
}

The transaction fields are only revealed for CONFIRMED/FAILED transactions in order to ensure the privacy of pending and rejected transactions.

Example of an endpointMsg response (varies depending on what each builder/OFA returns on their status API endpoint):

{ 
"error": "invalid sender", 
}

Fetching Transactions By OriginID

You can retrieve the entire history of your transactions using your originID on the following URL:

https://rpc.blocknative.com/boost/txs?originID=Donquixote

Understanding RPC responses

When an RPC receives the transaction, the RPC responds in one of two ways:

Without Error

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": "0xa129dc71038c20bd5cc58f08836c8616d2201581f203691d888878c734da189b"
}

With Error

{
    "id": 1,
    "error": {
        "code": -32603,
        "message": "invalid nonce"
    },
    "jsonrpc": "2.0"
}

Transaction Boost takes these responses and provides a human-readable status for each endpoint:

Endpoint Status

Transaction Status

Last updated