newTxs
, pendingTxs
include
tx_hash,tx_contents
[Default: all]duplicates
True,False
[Default]include_from_blockchain
True
[Default],False
filters
blockchain_network
Mainnet
[Default, Ethereum Mainnet], BSC-Mainnet
newTxs
is a stream of all new transactions as they are propagated in the BDN.pendingTxs
is a stream of all new transactions as they enter the Ethereum/BSC transaction pool.newTxs
feed. By design, the Gateway/Cloud-API do not perform the same detail of transaction validation that the Ethereum nodes do, and cannot completely guarantee that all transactions propagated are valid (e.g. the Gateway/Cloud-API do not check for double spends). Therefore, these transactions have had basic validations done (e.g. checksums and other sanity checks) but may not be accepted into the TxPool.pendingTxs
feed. Users planning to use pendingTxs
with a Gateway feed should enable validation against their local Ethereum node.newTxs
stream will perform faster than pendingTxs
. The performance difference can be significant (10-100ms). Users interested in timely transaction information could find newTxs
stream more appealing, while those who rely on strict correctness of the transactions data should utilize the pendingTxs
stream.newTxs
stream can send transactions that have been (a) previously confirmed hours or days prior, or (b) replaced by a higher priced transaction with the same nonce. It is recommended that users with latency sensitive applications track the latest nonce for each account and use it to filter out stale messages.include
section depends on the user's subscription plan:tx_hash
tx_hash
, tx_contents.from
, tx_contents.to
, tx_contents.value
, tx_contents.nonce
, tx_contents.gas
, tx_contents.gas_price
, tx_contents.max_priority_fee_per_gas
, tx_contents.max_fee_per_gas
tx_hash
, tx_contents.input
, tx_contents.v
, tx_contents.r
, tx_contents.s
, tx_contents.from
, tx_contents.to
, tx_contents.value
, tx_contents.nonce
, tx_contents.gas
, tx_contents.gas_price
,tx_contents.max_priority_fee_per_gas
, tx_contents.max_fee_per_gas
tx_hash
, tx_contents.input
, tx_contents.v
, tx_contents.r
, tx_contents.s
, tx_contents.from
, tx_contents.to
, tx_contents.value
, tx_contents.nonce
, tx_contents.gas
, tx_contents.gas_price
, tx_contents.max_priority_fee_per_gas
, tx_contents.max_fee_per_gas
, raw_tx
wss://<region>.<network name>.blxrbdn.com/ws
(e.g.wss://virginia.eth.blxrbdn.com/ws
for ETH)wss://api.blxrbdn.com/ws
.127.0.0.1
with default ws port 28333
in the examples below. By default, the WebSocket endpoint is ws://127.0.0.1:28333
for Python Gateway and ws://127.0.0.1:28333/ws
for Go Gateway.Authorization: <YOUR-AUTHORIZATION-HEADER>
) is done against --rpc-user
and --rpc-password
, which the Gateway started with. For Go Gateway, the header is always required for ws connection.