Skip to main content

2026-09-29

  1. Two Nodit-specific subscription types, nodit_pendingTransactions and nodit_minedTransactions, are now available for eth_subscribe in the EVM Node API. You can receive address-filtered pending transactions and mined transactions in real time over WebSocket.

Major Updates​

1. Mempool Transaction Subscriptions​

The default newPendingTransactions subscription type in eth_subscribe delivers only the hashes of all pending transactions. To track transactions for specific addresses, clients had to receive every hash, look each one up, and filter the results themselves. The two new subscription types apply address filters on the server and let you choose between hashes and full transaction objects in the response.

Itemnodit_pendingTransactionsnodit_minedTransactions
DeliversTransactions that entered the mempool and are not yet included in a blockTransactions included (mined) in a block
Address filterfromAddress, toAddress (OR condition)addresses ([{"to": "...", "from": "..."}])
Re-organized transactions-Set inclusion with includeRemoved
Response formatChoose hashes or full transaction objects with hashesOnlyChoose hashes or full transaction objects with hashesOnly
Supported networksEthereum mainnet, sepoliaEthereum, Polygon, BNB Smart Chain, Kaia, Avalanche, Arbitrum, Base, Optimism, Giwa, Arc

For both subscription types, pass the subscription type in params[0] of eth_subscribe and a filter option object in params[1]. Transactions are delivered without omission only within the WebSocket Bandwidth specified in Plans. If you omit the filter, all transactions on the chain are delivered.

{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_subscribe",
"params": [
"nodit_pendingTransactions",
{
"toAddress": ["0xdAC17F958D2ee523a2206206994597C13D831ec7"],
"hashesOnly": true
}
]
}

Compute Units (CU) are consumed based on the volume of subscribed data. We recommend filtering only the addresses you need and setting hashesOnly to true unless you need full transaction objects.