In brief
Transaction evidence moves through layers: wallet intent, node or mempool response, block inclusion, virtual processing, and accepted UTXO effects.
First Contact#
The word accepted can mean different things in different layers. Mempool accepted means a node admitted a transaction under mempool policy. Accepted evidence means consensus processing produced accepted transaction data and state consequences.
Working Model#
Mempool policy helps a node decide what it is willing to keep, relay, replace, or package. Consensus accepted evidence appears later in the lifecycle. A transaction can be locally useful before it has the later evidence an application should rely on.
Expanded Evidence Boundary#
The word accepted is dangerous unless the layer is named. A node may accept a transaction into its mempool under policy rules. That is useful: it can indicate the transaction is well-formed enough for that node's candidate pool and may be relayed or considered for templates. But it is not the same claim as consensus-visible accepted transaction evidence.
Accepted transaction evidence belongs later in the lifecycle, after block/DAG processing and virtual-state consequences. That later evidence is what applications usually need when they care about durable state. Mempool state is still important, but it is earlier, more local, and policy-shaped.
The page should train the reader to ask: accepted by what, at what layer, according to which source, and observed through which interface? If the answer is a mempool endpoint, label it mempool evidence. If the answer is accepted data or UTXO diff from the protocol source path, the claim can be stronger, subject to source review.