Skip to content
HodlCue

Reference

Blockchain

A blockchain is a decentralized, cryptographically secured distributed ledger that records transactions across an append only sequence of verifiable data blocks. Rather than depending on a single central authority, independent network nodes validate information according to mathematical consensus rules.

Core Architecture, Consensus, and Database Comparisons

Every block contains a list of validated transactions, a precise timestamp, a cryptographic nonce or validator signature, and the cryptographic hash of the preceding block header. Because each new block references the hash of the one before it, altering historical data invalidates every subsequent block header in the series. Network nodes immediately reject blocks with invalid hashes or altered records.

Consensus mechanisms such as Proof of Work and Proof of Stake enforce economic incentives for truthfulness. In Proof of Work, participants expend physical computational energy to solve cryptographic puzzles. In Proof of Stake, validators lock native tokens as collateral, risking automated slashing if they sign conflicting or invalid state updates.

Unlike standard distributed databases that coordinate read and write operations across multiple servers under a single administrative authority, a public blockchain operates without trusted root administrators, prioritizing censorship resistance and deterministic verification over raw transaction throughput.

Edge Cases, Network Splits, and Finality Failures

While blockchains are designed to create immutable ledgers, specific technical scenarios challenge stability and data finality:

  • Chain Reorganizations: When two block producers broadcast valid blocks almost simultaneously, the network temporarily diverges until the cumulative consensus rule resolves which branch survives, sometimes reverting recent transactions.
  • Hard and Soft Forks: Upgrades with backward incompatible rules split node software. Without unanimous node migration, persistent chain splits occur, creating distinct ledger histories.
  • Fifty One Percent Attacks: If an entity gathers majority control over mining hash power or staked capital, it can reorganize historical blocks to execute double spends.
  • Bridge and Smart Contract Vulnerabilities: Cross chain protocols that communicate ledger states can suffer validation mismatches, locking or minting unbacked assets outside base consensus.

Related terms

Back to glossary