Trusted Mode
Trusted Mode
Section titled “Trusted Mode”Trusted mode is ZEVM’s writable local development node.
Normative sources:
docs/specs/prd.mdanddocs/specs/json-rpc-contract.md.This page is an operational summary. For product-contract disputes, follow those normative sources.
What Trusted Mode Owns
Section titled “What Trusted Mode Owns”Trusted mode is the mode for local execution and local writes:
- core reads against local state
- simulation (
eth_call,eth_estimateGas) - transaction submission and mining
- canonical block, receipt, and log queries (including
eth_getLogs) - snapshots, revert, impersonation, state mutation, and time controls
- optional fork-backed reads with a local writable overlay
Filter lifecycle APIs beyond eth_getLogs are deferred.
Trusted mode also ships one exact deterministic managed dev-wallet contract. For mnemonic, derivation root, full address/key set, and signing behavior, see Managed Dev Wallet (Trusted Mode).
Naming And Alias Policy
Section titled “Naming And Alias Policy”- Canonical ZEVM controls use
zevm_* - Trusted mode accepts a fixed compatibility-alias set under
anvil_*, selectedhardhat_*, and selectedevm_* - Compatibility aliases are trusted-mode only
Compatibility alias acceptance is closed-world: only aliases explicitly enumerated on JSON-RPC reference pages are accepted.
Public docs should name zevm_* first, with aliases treated as compatibility inputs.
Trusted Config Shape
Section titled “Trusted Config Shape”{ "mode": { "trusted": { "chainId": 31337, "mining": { "type": "auto" }, "fork": null } }}Resolved unions:
mode.trusted.mining:{ "type": "auto" },{ "type": "manual" }, or{ "type": "interval", "blockTime": <seconds> }mode.trusted.fork:null,{ "url": "https://..." }, or{ "url": "https://...", "blockNumber": <u64> }
Trusted Block Tags
Section titled “Trusted Block Tags”| Tag | Meaning |
|---|---|
latest | current local head |
pending | alias of latest |
safe | alias of latest |
finalized | alias of latest |
earliest | block 0 |
| numeric quantity | exact local block number |
pending, safe, and finalized in trusted mode do not imply consensus finality.
Where To Go Next
Section titled “Where To Go Next”- Quickstart: Run Trusted Mode
- Quickstart: Forked Dev Node
- Reference: Trusted-Mode Configuration
- Reference: Core Reads
- Reference: Managed Dev Wallet (Trusted Mode)
- Reference: Simulation
- Reference: Transactions And Mining
- Reference: Blocks, Receipts, And Logs
- Reference: ZEVM Controls