What gives you mempool access
Two different things get called mempool access, and they have different requirements. On the EVM chains with a public mempool — Ethereum, Polygon, and BNB Smart Chain:
For a live feed of pending transactions, any node type is enough, in the full mode or the archive mode. The feed is the node’s view of the public mempool — transactions that reached it over the p2p network, not only the ones you submitted through it. No node sees every pending transaction, as each node’s view depends on its peers.
Global Nodes and Trader Nodes block
txpool_content, txpool_contentFrom, and txpool_inspect on EVM networks, in every mode and on every plan. A call returns error code -32601:
txpool_status is not blocked. It returns the pending and queued transaction counts on nodes whose client serves the txpool namespace, which varies by network and mode.
To read the pool contents, deploy a Dedicated Node and ask for the txpool_* namespace when you deploy. It is a customization that works in the full mode and the archive mode.
txpool_* is also a separate namespace from debug_* and trace_*, and each one has its own gate:
txpool_*— the node type decides whether you can read the pool contents, not your plan.debug_*andtrace_*— your plan enables them. They do not bringtxpool_*with them.
On protocols with no public mempool, pending-transaction methods like
eth_newPendingTransactionFilter and eth_subscribe("newPendingTransactions") return empty by design — pending transactions are visible only to the sequencer. On Base and Optimism, follow transactions in real time with Flashblocks instead — see the how-to guides (Base, Optimism) or how Flashblocks works (Base, Optimism).- Protocol — protocol name.
- Protocol availability — details of the mempool availability on the protocol level.
- Chainstack availability — what you need to deploy for the protocol’s pool-inspection methods on Chainstack.
- Client configuration — the default node client configuration for the mempool as deployed at Chainstack.
- Example — a simple curl example. Remember to replace YOUR_CHAINSTACK_NODE with your Chainstack node endpoint for that particular protocol.
