Ethereum (ETH) Identity: ethereum-mainnet / eip155:1 / native Version: pilot-1 / Method: 0.1.0 / Updated: 2026-10-03T12:00:00Z Verdict: Documented promise. Independent verification pending. Score: unrated / Coverage: 0% The original Ethereum paper describes programmable contracts, software that executes predefined rules. The foundation marks that paper as historical and directs readers to current documentation. The linked primary document is available. Its existence establishes what the project describes, while the operational checks remain open. Current ownership concentration, privileged control powers, independently measured usage, incident remediation and locally executable liquidity remain unverified in this pilot. The evidence coverage is insufficient for an overall score. A documented mechanism alone cannot establish current resilience or expected returns. Reproducible network observations, current control maps, documented supply rules and independent incident records would allow the pending checks to be evaluated. Promise and Scope This dossier examines native ETH on the Ethereum mainnet (eip155:1) through documented mechanisms for computational fees, staking, and offchain governance. The scope is limited to project documentation and historical specifications. It does not verify current network state, ownership concentration, or live deployment metrics. Sources: Governance Structure Ethereum.org describes an offchain governance model (discussion and decisions outside the blockchain) where proposal authors, client developers, node operators, validators, application developers, users, and ETH holders participate through discussion and software adoption. An Ethereum Improvement Proposal (EIP) outlines a proposed change. Acceptance, implementation, and network activation are distinct steps. Developers can decline to implement changes, and operators can decline upgrades. Holding ETH does not grant a standing automatic protocol vote. The documentation cites the 2016 response concerning the DAO application as a historical example of social coordination leading to incompatible chains, specifically Ethereum Classic. This record describes the process but does not measure present influence or guarantee that contract losses will be reversed in future incidents. Sources: https://raw.githubusercontent.com/ethereum/ethereum-org-website/5cae093227c2de78c827bf9afdac90adbb7ad3ea/public/content/governance/index.md Computational Fees and Gas Gas is defined as a measure of computational effort required to execute operations on the network. Fees are paid in ETH. The base fee is burned, meaning it is removed from circulation, while a priority fee goes to the validator processing the block. A failed transaction can still consume gas. These mechanisms describe how costs are structured but do not establish net supply changes, current user costs, adoption rates, or income for token holders. Sources: https://raw.githubusercontent.com/ethereum/ethereum-org-website/dev/public/content/developers/docs/gas/index.md Staking and Security Validators stake ETH to check or propose blocks. Misbehaviour by a validator can lead to the destruction of their staked ETH. This identifies a security role for ETH within the proof-of-stake consensus mechanism. However, these descriptions do not measure today's validator concentration, the number of independent operators, software diversity among clients, realized rewards, or overall network resilience. Sources: https://raw.githubusercontent.com/ethereum/ethereum-org-website/dev/public/content/developers/docs/consensus-mechanisms/pos/index.md Hypothetical Fee Calculation The EIP-1559 specification details execution gas fees. The priority fee is capped at maxFee minus baseFee. Unused gas is refunded at the effective gas price. For ongoing blocks, the target is half the parent gas limit, with integer base-fee adjustment using denominator 8 and a minimum upward increment of 1. Initial fork handling differs from this standard calculation. All inputs below are hypothetical examples provided by Cryptosnif arithmetic (platform-mechanisms-1). They do not represent current network conditions. Inputs: Gas used: 21000 Gas limit: 30000 Base fee: 30 gwei Max fee: 40 gwei Max priority fee: 2 gwei Calculated Outputs: Total cost: 672000000000000 wei (0.000672 ETH) Burned amount: 630000000000000 wei (0.000630 ETH) Priority fee: 42000000000000 wei (0.000042 ETH) Refund for 9000 unused gas: 288000000000000 wei (0.000288 ETH), excluding other refund mechanisms. Conversion notes: 1 gwei equals 1000000000 wei. 1 ETH equals 10^18 wei. Base Fee Adjustment Example: At parent base fee 30 gwei, parent gas limit 30000000, and target 15000000: The next base fee is 33.75 gwei after a full parent block. The next base fee is 26.25 gwei after an empty one. These figures illustrate the specification logic. No present fees or net ETH issuance are inferred from this example. Sources: https://raw.githubusercontent.com/ethereum/EIPs/ba6c342c23164072adb500c3136e3ae6eabff306/EIPS/eip-1559.md Unknowns and Limitations Current ownership concentration, privileged control powers, independently measured usage, incident remediation history, and locally executable liquidity remain unverified in this pilot review. The evidence coverage is insufficient for an overall score. A documented mechanism alone cannot establish current resilience or expected returns. Sources: Verdict Documented promise. Independent verification pending. The available sources confirm the existence of specific governance processes, fee structures, and staking roles. They do not validate the operational status, economic outcomes, or security posture of the live network. Different fee inputs cannot establish a cost winner without broader comparative data. Sources: https://raw.githubusercontent.com/ethereum/ethereum-org-website/5cae093227c2de78c827bf9afdac90adbb7ad3ea/public/content/governance/index.md, https://raw.githubusercontent.com/ethereum/ethereum-org-website/dev/public/content/developers/docs/gas/index.md, https://raw.githubusercontent.com/ethereum/ethereum-org-website/dev/public/content/developers/docs/consensus-mechanisms/pos/index.md What Would Change This Reproducible network observations, current control maps, documented supply rules, and independent incident records would allow the pending checks to be evaluated. Until such evidence is supplied, the assessment remains limited to the described mechanisms. Sources: Source: https://ethereum.org/whitepaper/ Claim: The project publishes the mechanism described above. Observed: 2026-10-03T12:00:00Z Expires: 2026-11-02T12:00:00Z