Ethereum Magicians debate six-field RVR receipt standard

A discussion draft for Recomputable Verification Receipts showed up on Ethereum Magicians on August 27, 2026. The goal, stated plainly: produce a verifiable, recomputable record of transaction execution that doesn’t rely on a transaction hash as the whole story.

Current baseline is v0.0.1-rc.2. The frozen release is tagged at commitf4476754c92e0bea549474722108ec60ded1385a. TheverificationProfileDigest isac16ba13abe00d8b7fac14bf5c35ee3175de3dbd7d70a296be27a094a99ef29c, and thepackageDigest ise2c7712e4ce5551628cf2d1b65b0ae4458d5d2f7aaed7ffd3c969505ee29d63c. These are exact values from the draft itself, not projections.

Six fields. That’s the structure:claimDigest,evidenceSetDigest,verificationProfileDigest,outcome,reasonCode, andresultDigest. Everything in the document’s technical core flows from that set.

The underlying problem the draft is trying to solve is real enough. Ethereum’s existing standards and draft proposals frequently use opaque commitments likeevidenceHash andproofHash that leave verification semantics up to whatever system is consuming them. The RVR draft argues this pushes the hard semantic work downstream, where it gets reinvented, incompatibly, over and over. The proposed fix is to define the verification contract and the outcome-relevant closure of those artifacts in the receipt itself, so the execution record can actually be recomputed by a third party rather than trusted on presentation.

For protocol teams building on off-chain computation or layer-2 infrastructure, the pitch is a shared receipt format they don’t have to roll themselves.

The interoperability argument is the strongest thing in the proposal. A verifier working from a standardized receipt could assess a claimed execution outcome through named digests and result data rather than treating a transaction hash as a complete accounting of what actually ran. Whether six fields can carry all the necessary verification semantics without forcing awkward compromises is precisely what the Ethereum Magicians thread is trying to work out — and the draft’s authors haven’t closed that question.

Be clear on where this stands: RVR hasn’t reached Standards-Track ERC. The discussion post explicitly solicits design and scope feedback, which means the baseline could shift materially before anyone makes a standardization call.

ETH was trading at $2,485.21, up 1.2% over the prior 24 hours, per CoinGecko. That move has no apparent connection to a spec proposal that has no confirmed protocol deployment attached to it.