“Mempool is not a ledger” is not just a slogan; it’s a very practical boundary. A typical mempool does not include a prequeue: deferred transactions for future nonces won’t appear in the ordinary response. Even if one node has seen a particular transaction, that does not prove that all nodes have seen the same transaction, or that it has already entered the final ledger.
The reason is that mempool is local. Each node’s mempool is not identical; transactions may be evicted, replaced, or expire. Deferred in RUES indicates a transaction is staged and waiting for conditions—it is not the same state as being confirmed in a block. An empty query result might mean the current node doesn’t have that transaction, which does not automatically mean the network never received it.
So, when judging a transaction, look at it in separate dimensions: what is the pending view of the local node? Is the transaction in deferred status? Has it entered a block? Where is the evidence of finality? Treating the mempool page screenshot as the whole network ledger, or treating deferred as failure and completion, will cross state boundaries.
When watching @Dusk’s transaction status, <$DUSK > is only a native token; you cannot turn the local pending view into a network-wide conclusion. <#dusk > can be monitored for changes, but the final judgment still requires block and state evidence.
Similarly, replacement or expiration shows that the mempool is a dynamic cache, not a permanent record. If readers want to confirm a transaction’s outcome, they should turn to blocks, state, and finality evidence—not repeatedly refresh a particular node’s local list. For <@Dusk >, the pending view of <$DUSK > and the settled state must be kept separate; <#dusk > cannot turn what you see locally into the whole network ledger. A local list only tells you what this node sees at the moment. The boundary of the query result determines what further judgment it can support.
The reason is that mempool is local. Each node’s mempool is not identical; transactions may be evicted, replaced, or expire. Deferred in RUES indicates a transaction is staged and waiting for conditions—it is not the same state as being confirmed in a block. An empty query result might mean the current node doesn’t have that transaction, which does not automatically mean the network never received it.
So, when judging a transaction, look at it in separate dimensions: what is the pending view of the local node? Is the transaction in deferred status? Has it entered a block? Where is the evidence of finality? Treating the mempool page screenshot as the whole network ledger, or treating deferred as failure and completion, will cross state boundaries.
When watching @Dusk’s transaction status, <$DUSK > is only a native token; you cannot turn the local pending view into a network-wide conclusion. <#dusk > can be monitored for changes, but the final judgment still requires block and state evidence.
Similarly, replacement or expiration shows that the mempool is a dynamic cache, not a permanent record. If readers want to confirm a transaction’s outcome, they should turn to blocks, state, and finality evidence—not repeatedly refresh a particular node’s local list. For <@Dusk >, the pending view of <$DUSK > and the settled state must be kept separate; <#dusk > cannot turn what you see locally into the whole network ledger. A local list only tells you what this node sees at the moment. The boundary of the query result determines what further judgment it can support.