eth Scope

eth targets Ethereum toolkit functionality with conservative defaults.

In Scope

Bounded canonical decoding of execution-layer data.
Typed transaction envelopes and fork-aware validation.
Header, receipt, transaction, and proof verification.
First-party audited EVM execution and execution-layer state transition for claimed forks.
Genesis import, block validity, trie-root construction, blob/KZG boundaries, and full execution fixture admission before broad execution support is claimed.
Core dependency independence reviews for hashing, signatures, execution, consensus, networking, and RPC semantics.
Optional REVM adapter only as a temporary/reference path after dependency admission passes.
Optional RPC client policy with explicit trust models.
Optional signer boundary with external-signer-first design.
Optional Reth integration at adapter boundaries.
Optional ABI, contract-standard, ENS, consensus, Engine API, networking, txpool, sync, and node-adjacent boundaries after their versioned roadmap gates.
Conformance evidence against pinned upstream test revisions.

Full execution-client behavior unless each required boundary has a versioned implementation and verification path.
Any core Ethereum behavior backed only by a third-party implementation unless it is explicitly classified as an optional backend, reference adapter, compatibility adapter, temporary debt, or cryptographic exception with conformance evidence.
Consensus, Engine API, and beacon behavior outside the scheduled optional consensus milestones.
Validator-adjacent behavior until the mining, builder, and validator boundary decision milestone completes.
P2P networking in default builds.
Hardcoded public RPC endpoints.
Implicit transaction broadcast fanout.
Local key storage as a default feature.
Marketing claims that no_std alone provides security.