Subscribe Bundle
Introduction
Currently, Searcher can receive bundle stream from Scutum without subscribing to a plan.
The bundle stream of Scutum is based on the SSE protocol and pushed uniformly in the form of a bundle, including transactions submitted via eth_sendRawTransaction
and bundles submitted via eth_sendMevBundle
. Transactions in the data stream are uniformly desensitized and only authorized transaction data is disclosed.
Searcher can obtain data through the RPC endpoint to execute the backrun strategy. To avoid data interruption due to network fluctuations, it is recommended to establish a reconnection mechanism.
RPC Endpoint
Ethereum:https://eth.blockrazor.xyz/stream
BSC:https://bsc.blockrazor.xyz/stream
Rate Limit
Data stream limit:5 Streams / IP
Bundle Type
Raw Bundle
Raw Bundle refers to the bundle that has not been implemented by Scutum's Searcher with the backrun strategy. Transactions in Raw Bundle come from two channels.
Transactions submitted through eth_sendRawTransaction
will be automatically constructed as a bundle by Scutum and pushed to Searcher to execute the backrun strategy. The Raw Bundle in this scenario only contains one transaction;
For the Raw Bundle submitted through eth_sendMevBundle
, the transactions come from the public mempool or are self-constructed. The Raw Bundle in this scenario can contain up to 50 transactions.
First Backrun Bundle
After the Searcher executes the backrun strategy on Raw Bundle, it can choose to continue to disclose the bundle to other Searchers to execute the nested backrun strategy. At this time, the bundle disclosed to the data flow is the First Backrun Bundle, which contains all transactions in Raw Bundle, and one backrun transaction.
Data Stream Structure
Bundle
Patameters | Format | Remark |
---|---|---|
chainID | string | ETH: 1, BSC:56 |
hash | string | bundle hash, data streams are pushed uniformly in the form of bundles |
transactions included in bundle | ||
nextBlockNumber | uint64 | the block number where the bundle is going to be included |
maxBlockNumber | uint64 | the maximum block number valid for this bundle |
proxyBidContract | string | proxy contract address of bundle bidding, biding call for detail can be found in Send Bundle. |
refundAddress | string | input parameter of bidding call, the bidding will be refunded to refundAddress in proportion. |
refundCfg | int | input parameter of bidding call |
state | []state | state change of state objects in EVM, data stream example |
txs
Patameters | Format | Remark |
---|---|---|
hash | string | transaction hash |
from | string | sender of the transaction |
to | string | receiver of the transaction |
value | hex | value being transacted |
nonce | uint64 | nonce |
calldata | string | calldata |
functionSelector | string | the first 4 bytes of the contract function signature hash |
gasLimit | uint64 | gas limit |
gasPrice | uint64 | gas_price |
logs | event logs emitted during transaction execution |
log
Patameters | Format | Remark |
---|---|---|
address | string | the smart contract address that triggered the event |
topics | []string | event log topcis |
data | string | storage area for non-index data |
state
the default data stream does not contain state
field, if you need it, please modify the url of RPC Endpoint to
Patameters | Format | Remark |
---|---|---|
"0x7C3b……3cb9E2" | []string | The address of the state object where the data changes, which can be EOA or smart contract |
"0x935b……6cf608" | string | the Key of the changed data in state object |
"0x0000……3ffc00" | string | the Value of changed data in state object |
Data Stream Example(default)
Data Stream Example(including state)
The default data stream does not contain state
field, if you need to obtain it, please modify the url of RPC Endpoint to
Last updated