Verify execution success, consensus finality and the business outcome separately.
A receipt answers an execution question
An Ethereum transaction receipt can show that a transaction was included and whether execution succeeded. It does not, by itself, answer every question about the stability of that block or the outcome of an external workflow. A successful contract call might request a withdrawal, create an order or emit an event. Its intended downstream consequence could require additional processing after the receipt appears.
Finality concerns accepted history
Ethereum's proof-of-stake consensus distinguishes the current chain head from justified and finalised checkpoints. Finality depends on validator voting and the protocol's economic security assumptions, not simply a wallet's animation. Reversing finalised history would represent a serious consensus failure with slashable stake under the protocol model. This is a different security statement from saying that a recently included block has accumulated a familiar number of successors.
Use three columns in an audit
Consider a hypothetical payment integration. Column one records execution success and the actual recipient event. Column two records the block and its observed finality status. Column three records whether the merchant credited the invoice. These columns can disagree temporarily without any evidence of fraud. For example, the chain may finalise normally while the merchant's indexing service is delayed. Conversely, a fast internal credit may precede the merchant's chosen finality threshold.
Define completion before sending
Ask the receiving service what chain state it requires and what happens during finality delays. Avoid presenting a normal expected duration as an unconditional deadline. Check the chain, contract, transaction result and application record before retrying an operation; a second successful call might create a second order rather than fix the first. The useful habit is to state precisely what has been verified and leave unobserved stages marked pending instead of compressing every stage into the word done.
Sources & context
Sources checked 7 October 2026. This is explanatory coverage, not personalised investment advice. Our corrections policy.
