Blockchain
Append-only ledger of blocks secured by cryptography.
A blockchain is a shared digital ledger whose accepted transactions are grouped into ordered blocks and verified under common consensus rules. Cryptographic hashes connect data and make unauthorized changes detectable. Multiple participants can maintain and audit the ledger without relying on one organization to be the sole record keeper.
When users submit transactions, nodes check signatures and protocol rules. A miner or validator proposes an ordered block, and the network's consensus process determines whether it becomes part of canonical history. Each node can independently verify the result and calculate current state, such as account balances or smart contract storage. Public blockchains generally allow broad participation, while permissioned blockchains restrict validators or readers.
Blockchains matter when parties need a common record but cannot or do not want to appoint one trusted database owner. Bitcoin uses its blockchain for peer-to-peer value transfer. Ethereum adds programmable smart contracts that support tokens, exchanges, lending, and other applications. Supply chains and institutions sometimes use distributed ledgers, although a normal database is often simpler when one trusted operator already exists.
The technology has real limits. Consensus duplicates work across nodes, making on-chain storage and computation more expensive than centralized infrastructure. Public transactions can expose sensitive activity. A blockchain can prove what participants submitted, but it cannot independently know whether an off-chain claim is true. Oracles, custodians, bridges, and administrators introduce additional trust and failure points.
Immutability is also conditional. Recent blocks can be reorganized, protocol communities can change software rules, and smart contract administrators may upgrade application behavior. Strong finality and decentralized validation make history difficult to alter, not magically impossible. Smart contract bugs, stolen keys, scams, and misleading interfaces can still cause irreversible losses even when the underlying chain works correctly.
Evaluate a blockchain by its consensus security, validator distribution, client diversity, finality, fees, data availability, governance, and operational record. Transaction speed alone says little about resilience or decentralization. Developers should keep private data off public ledgers, minimize expensive state, and plan for reorgs and outages. Users should verify networks, addresses, and contract permissions. Blockchain is useful infrastructure for shared verification, not a universal replacement for databases, laws, or trust.
Frequently asked questions
- Blocks contain cryptographic commitments to data and references to prior history. Independent nodes reject changes that violate consensus rules, while proof of work or proof of stake makes replacing accepted history economically and operationally difficult. Security is not absolute. It depends on decentralization, participant incentives, client software, finality, and the attacker's resources.
- Blockchains can record payments, fungible tokens, NFTs, identity attestations, governance votes, and smart contract application state. They work best when several parties need shared, verifiable records without one operator controlling updates. Large files, secret data, cheap high-volume computation, and facts about the physical world usually require off-chain storage, privacy systems, or trusted oracles.
- Networks differ in consensus, validator requirements, programming model, block capacity, fees, finality, privacy, governance, and data availability. Improving speed can increase hardware demands or reduce decentralization. Some chains prioritize simple monetary settlement, while others support general smart contracts. Compare actual security assumptions and user needs instead of relying only on advertised transaction-per-second numbers.