Skip to content

Ethereum

Ethereum is a public blockchain for smart contracts and decentralized applications. This entry explains how its execution layer, proof-of-stake consensus, ETH fees, and Layer 2 ecosystem fit together, and where users still face operational and application risk.

Updated

For educational purposes only; not investment advice. Investing may result in loss.

Direct answer

Ethereum is a public blockchain whose state can be changed by transactions that transfer ETH or call smart contracts. Unlike a ledger limited to predefined transfers, it lets developers publish programs that all participating nodes execute under the same protocol rules. Those programs support wallets, exchanges, lending markets, stablecoins, games, and many other applications.

ETH is Ethereum’s native asset. Users pay execution fees in ETH, validators stake ETH to help secure proof-of-stake consensus, and applications can use ETH as collateral or a unit of account. ETH is not a share in a company and does not guarantee a return.

1
Create

A wallet constructs a transaction with destination, value, fee parameters, and replay-protection data such as spent inputs or a nonce.

How it works

A wallet creates and signs a transaction with the sender’s private key. The transaction names a recipient or contract, an amount, optional call data, a nonce, and fee limits. An execution client checks the signature and account state, then runs the transaction in the EVM. Every node that accepts the block re-executes the same instructions, so a valid state transition can be reproduced by other nodes. A reverted contract call does not undo the work already performed, so it can still consume gas.

Ethereum uses a market-based fee mechanism. Gas measures computation and storage work; the amount paid depends on gas used and the applicable fee per unit. EIP-1559 separates a protocol-set base fee, which is burned, from a priority fee paid to the validator that includes the transaction. A higher fee can improve inclusion chances, but it cannot make a failing contract condition true.

Proof of stake divides time into slots and epochs. A selected validator proposes a block, other validators attest to it, and the fork-choice rules select the chain with the greatest attestation weight. Checkpoint votes can make blocks economically final; a short reorganization can still occur before finality. Layer 2 networks execute many transactions away from Ethereum mainnet and post data or proofs back to it, but each bridge, sequencer, and withdrawal process has its own trust and timing assumptions.

Example

Suppose Xiao Chen has 1 ETH and swaps 0.2 ETH for a stablecoin on mainnet. The wallet estimates 150,000 gas and a fee of 25 gwei per gas. If all gas is used, the network fee is about 0.00375 ETH. The router checks that the result meets the minimum received amount; if the price moves too far before execution, the call reverts, Xiao Chen keeps the swap amount, and the used gas is still charged.

Another user deposits 500 USDC from Ethereum mainnet into an optimistic Layer 2. A bridge contract records or locks the mainnet funds, and the Layer 2 issues the corresponding representation. The user pays the Layer 2’s fees, but a normal transfer does not move the asset back to mainnet. A canonical withdrawal may include a challenge waiting period, while a third-party liquidity bridge adds contract and liquidity-provider risk. The same address and ticker do not prove that two balances are on the same network.

If a lending protocol holds 10,000 ETH as collateral and receives a price from an oracle, its contract can allow borrowing or trigger liquidation according to the collateral ratio. Ethereum makes every node follow the deployed code, but it does not guarantee that the code, oracle, governance process, or collateral price is sound. Removing a human approval step moves risk into those technical and economic dependencies.

Risks

Before using an Ethereum application, verify the wallet network, website domain, contract address, function, amount, authorization scope, minimum received amount, and fee settings. After signing, keep the transaction hash and inspect its status and events in an independent block explorer. Token names and wallet simulations are not proof of identity or final execution, because symbols can be duplicated and state can change before inclusion.

Separate protocol risk from application risk. Healthy Ethereum consensus does not prove that a lending market is secure, and a paused application does not mean the mainnet has stopped. Review execution logic, oracle design, upgrade administrators, timelocks, governance concentration, front-end dependencies, and the asset itself. Test with a small amount, limit approvals, set explicit slippage, and confirm how funds can exit; these controls reduce mistakes but do not protect principal or price.

Wallets and RPC providers can show stale balances or fail to broadcast transactions. Cross-check important information with a trusted explorer or another provider, and do not repeat a transfer solely because a page looks stuck. A private-key signature authorizes an account; it does not certify the destination, contract code, or economic outcome.

Composability lets one transaction call several protocols, so a failure or exploit can propagate through routers, pools, wrapped assets, and token contracts. Larger transactions deserve a small test and a clear unwind path. Network upgrades are adopted by node software; ordinary holders do not send ETH to an “upgrade address.” Any page requesting a seed phrase, private key, or unlimited approval in the name of an upgrade, merge, or airdrop is a high-risk phishing attempt.

Common misconceptions

Myth 1: ETH is a share of the Ethereum company

Ethereum is not a company whose shareholders receive rights through ETH. ETH is the network’s native asset, used for fees, staking, and on-chain transactions. Its price risk is not the same as analyzing equity in a corporation.

Myth 2: Smart contracts mean there is no risk

Automatic execution means that nodes apply the published code; it does not mean the code is correct or the inputs are honest. Bugs, privileged keys, oracle failures, governance decisions, and mistaken signatures can still cause irreversible losses.

Myth 3: Mainnet and Layer 2 share one balance

Mainnet and a Layer 2 are separate execution environments. Check the network, token contract, bridge status, and withdrawal rules before and after moving funds. A matching wallet address does not make balances interchangeable.

Sources

Navigation

Search the wiki...