Blockchain Foundations

Blockchains are replicated ledgers whose participants use a consensus protocol to order transactions and agree on state.

Protocol rules are enforced by software and network participants rather than a single database operator. People and institutions still write the code, run infrastructure, govern upgrades, and provide interfaces.

That distinction changes which parties can validate, block, or reverse a ledger update.

How blockchains work

At their core, blockchains operate through decentralized networks of computers that validate, agree upon, and record transactions.

1. A user submits a transaction to the network.
2. Block producers group transactions into batches called blocks.
3. The network reaches consensus on which blocks are valid.
4. Accepted blocks extend the chain or ledger history.
5. Rewriting settled history becomes harder as the network adds more work or finalizes more state, depending on the consensus design.

Miners or validators may earn protocol rewards and transaction fees, depending on the network. Other participants, including users and non-producing nodes, do not necessarily receive compensation.

Wallet interfaces can hide this process, but the consensus and finality rules still determine what a transaction confirmation means.

Consensus

Consensus mechanisms are the backbone of blockchain networks.

They allow participants who may not know or trust each other to agree on a valid ordering of ledger updates without relying on one database operator. Consensus cannot determine whether an off-chain claim is true.

This model can reduce reliance on a central counterparty, but it does not remove counterparty or implementation risk from every application built on it.

"Trustless" is shorthand, though, not an absolute. Users still trust that the contract code does what it claims, that validators in aggregate stay honest, and that their wallet software and the frontend they're clicking through aren't lying to them. What changes is who you trust and how visible that trust is, not whether trust exists.

Consensus designs also differ in concrete ways. Bitcoin's proof-of-work offers probabilistic finality: a transaction becomes practically irreversible only as more blocks are built on top of it. Ethereum's proof-of-stake finalizes checkpoints after at least two epochs under normal network conditions. Protocols based on Byzantine fault tolerant designs can offer faster deterministic finality, subject to their own participation and fault assumptions. "Confirmed" means different things on different chains.

To engage with a blockchain, users or contracts use accounts that hold state, assets, permissions, or executable code, depending on the network.

On public permissionless networks, generating a key pair does not require an institution's approval. Using the network still requires connectivity, fees, compatible software, and compliance with applicable law.

Control follows the keys, but not always simply: multisig accounts split control among several signers, upgradeable contracts leave power with whoever holds the admin key, custodial interfaces hold keys on the user's behalf, and some tokens can be frozen by their issuer regardless of whose wallet they sit in. "Only the owner has control" is the starting point, not a guarantee.

Accounts and wallets

Some vocabulary worth keeping straight: a private key is a secret used to authorize actions; a signer is whatever holds that key and produces signatures, such as an app, a hardware device, or several parties in a multisig; an address is a public identifier; and a wallet is software or hardware used to manage keys and accounts. The exact model varies. Ethereum tracks account state, while Bitcoin records spendable transaction outputs.

State-changing transactions generally require a fee. Reading public state is usually free to the reader, and some applications sponsor user transactions.

Fees price scarce block space, compensate infrastructure or validators, and discourage spam. Their size varies widely by network and demand.

Unlike traditional systems constrained by business hours, holidays, intermediaries, and geographic limits, blockchain-based markets operate globally and continuously.

The protocols can operate continuously, although wallets, interfaces, exchanges, and internet access can still fail or restrict users.

Transparency, traceability, and privacy

Most public blockchains are transparent by default. Transactions, balances, and contract code are visible to anyone through block explorers, which are tools that let users:

• Inspect broadcast and confirmed transactions
• Inspect wallet histories
• Analyze network health and activity
• Review verified smart-contract code when the source has been published

This transparency is common, but not absolute. Some blockchains incorporate privacy features or enable optional confidentiality for users and applications that require it.

Smart contracts and on-chain logic

Blockchains like Ethereum, Solana, and others support smart contracts, programs stored on-chain whose functions execute when transactions call them. These contracts are the scaffolding of decentralized applications (dApps), enabling everything from automated exchanges and lending platforms to on-chain games and digital identities. Some contracts are immutable, while others can be upgraded, paused, or governed through admin keys. Contracts can enforce on-chain rules, but claims involving physical goods, identity, or law still need external systems.

Censorship resistance is a spectrum

One of the philosophical pillars of blockchain is censorship resistance: the idea that no one should be able to prevent others from participating, building, or transacting.

Generating a wallet does not require a credit check. Access to a particular asset or application may still depend on issuers, interfaces, infrastructure, and jurisdiction.

But while that's the ideal, reality is more nuanced.

Censorship resistance exists on a spectrum.

It depends on factors like validator decentralization, node distribution, reliance on centralized infrastructure, and more.

The Nakamoto Coefficient estimates the smallest set of entities that could compromise a chosen subsystem. It captures concentration in that subsystem, not a network's total decentralization or censorship resistance.

Still, even highly decentralized chains can face pressure points such as centralized RPC endpoints or geographic restrictions imposed by governments or service providers.

Due diligence

Before using a network or application, identify who can upgrade or pause it, which parties control validators and infrastructure, how finality works, what the wallet asks you to sign, and how funds can be recovered after an error or failure. Published code and on-chain activity help, but neither replaces that review.