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, a full-mode node is enough. 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.
The
txpool_* namespace is the part that needs the archive mode. A Dedicated Node can serve txpool_* in the full mode too — that one is a customization, so ask for it when you deploy.
txpool_* is also a separate namespace from debug_* and trace_*, and each one has its own gate:
txpool_*— the node mode enables it, not your plan. It works on an archive node even when your plan has no debug and trace access.debug_*andtrace_*— your plan enables them. They also work on full-mode nodes, and they do not bringtxpool_*with them.
txpool_content on such a node returns:
txpool_* methods, deploy the node in the archive mode, or ask for them on a full-mode Dedicated Node. Trader Nodes are regional and not every region offers the archive mode, so check Available clouds, regions, & locations for your region before you deploy.
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.
