How Ethereum's state, gas and finality fit together

Ethereum is a programmable Layer 1 whose account state, transactions, proof-of-stake consensus, gas market and smart contracts operate as one system. Its account model tracks balances and contract data directly, while transactions carry the instructions that update that global state. Finality progresses through slots, epochs, checkpoints and validator attestations, with each epoch containing 32 slots.

A transaction can transfer ETH, call a contract or deploy new code. Its envelope includes a chain ID, nonce, destination, value, calldata, gas settings and a signature. After signing, it can enter the public mempool or a private relay. Validators and builders include valid transactions in blocks, execute them against the current state and record changes to balances, nonces, contract storage and gas accounting.

Why it matters

Ethereum's account-based design differs from Bitcoin's UTXO model and is built for persistent application logic. Contract Accounts hold code and state, while Externally Owned Accounts controlled by private keys initiate transactions. This structure lets Ethereum support exchanges, lending markets, games, governance and other applications rather than only value transfers.

Gas prices computation and limits how much network work a transaction can consume. Under EIP-1559, the base fee adjusts with block demand and the priority fee acts as a user-selected tip. The result is a resource-pricing system in which transaction cost reflects computation, blockspace demand and urgency.

Market impact

Smart contracts make the base layer programmable, and token standards make that functionality interoperable. ERC-20 supports fungible tokens, ERC-721 supports unique assets, and ERC-1155 supports multiple token types. WETH provides an ERC-20 representation of ETH for DeFi integrations, while events, approvals and allowances help applications recognize and move assets consistently.

Account abstraction expands the wallet design space through ERC-4337. User Operations, bundlers, the Entry Point, aggregators and paymasters can support sponsored fees, batched actions, social recovery and flexible verification without changing Ethereum consensus. Alternative Layer 1s such as Solana, Avalanche, Sui and Aptos make different choices around throughput, validator design, execution and modularity. The key comparison is not speed alone, but the security, decentralization and hardware assumptions behind each design.