# Ethereum Draft Seeks Reproducible Transaction Simulations

Published 2026-10-31 · Crypto.world Team · Crypto.world

> A draft ERC proposes a common format for simulators to produce results that wallets and hardware devices can independently check. The draft remains open for discussion, including how devices would verify the Ethereum state behind a simulation.

> “Standardizes the format, hashing, and verification of simulation results so that any compliant simulator produces identical canonical output for the same inputs.”
>
> MATOBOYCRYPTO65, draft author

A draft ERC posted to Ethereum Research on October 30 proposes a standard way for separate wallets, hardware devices and other verifiers to reproduce transaction-simulation results. The proposal, titled “Independent Simulation Result for (STVA),” is marked as a draft standards-track ERC, not an adopted Ethereum standard. Its stated aim is to let a signer check a transaction’s effects without relying solely on the frontend that presented it.

## One payload, one canonical result

The draft calls for simulators to receive the complete transaction preimage, including fields used in its hash, along with a block or state root, or Merkle proofs for relevant state. Optional overrides may also be supplied. The proposed inputs cover a transaction, a UserOperation or a SafeTx.

Each simulator would produce a structured SimulationResult. The listed fields include success status, gas used, return data, logs, state changes or a hash of those changes, structured balance changes and token transfers, a snapshot identifier, and simulator version. A semantic summary is optional.

The result would receive a canonical hash, either through keccak256 over an ABI-encoded result or a domain-separated EIP-712 hash. The draft’s goal is for independent simulators given the same inputs to produce the same canonical output, giving a signing device a specific result to check rather than an unstructured display supplied by a website.

## Three verification levels, with different trust assumptions

The draft sketches three compliance levels. Basic allows any simulator; Standard adds agreement among multiple nodes on the state root; Strict calls for local revm or EVM execution with Merkle proofs of the pre-execution state.

For an offline hardware verifier, the proposed requirement is to re-execute the transaction or verify the supplied proofs, then reject a result that does not match. The draft does not specify a finished proof format or settle how a device anchors a witness to a trustworthy recent block. Those questions matter because matching outputs are only as dependable as the state each simulator evaluates.

## State proofs and result encoding remain open

The proposal itself flags three design choices for discussion: whether to include a full state diff or only its hash, whether to require prestate proofs or allow trusted RPC data backed by multi-node consensus, and how tightly to bind the result to the VerificationPayload and capability tokens. The draft suggests simulation hashes could be bound into signatures and Scoped Capability Tokens, linking a reviewed transaction result to later authorization.

A reply posted on October 31 asks whether the signing device would carry an EVM engine and receive a Merkle-proven witness, and how it would anchor that witness to a recent block hash. The question goes to a central engineering trade-off in the proposal: local execution and proof checking can reduce reliance on a frontend, but require the signing device to verify a sufficiently trustworthy view of Ethereum state.

The draft frames simulation as a machine-checkable artifact, but it does not establish a deployed standard or prescribe a single verification model. Its immediate contribution is a proposed result format and a set of unresolved choices for ERC discussion; the thread’s October 31 reply puts state authenticity among the first issues those choices must address.

## Sources

1. Original source [Ethereum Research](https://ethresear.ch/t/erc-draft-independent-simulation-result-for-stva/26198) ethresear.ch

## Related stories

- [Ethereum Draft Defines Risk Reports for AI-Signed Transactions](https://crypto.world/news/ethereum-draft-agent-pre-sign-risk-report)
- [Researchers Find 4.67M Malicious EIP-7702 Delegations](https://crypto.world/news/researchers-find-4-67m-malicious-eip-7702-delegations)
- [Electrum 4.8.3 Patches Bitcoin Wallet Transaction-Spoofing Flaw](https://crypto.world/news/electrum-4-8-3-bitcoin-wallet-transaction-spoofing-fix)
- [Researchers Find 9 of 10 AI Models Raised Their Own Circle Wallet Caps](https://crypto.world/news/ai-models-raised-circle-wallet-spending-caps)
- [Predict.fun Wallet Drains Hit $398,000 Across 29 Accounts](https://crypto.world/news/predict-fun-wallet-drains-398000-29-accounts)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/ethereum-draft-reproducible-transaction-simulation-results
