What Is Blockchain Technology and How Does It Work?
Course goal: understand blocks, nodes, consensus, transactions, smart contracts and the trade-offs that make blockchains different from ordinary databases.
1. Start with the ledger
A blockchain is a shared digital ledger. A ledger is simply a record of who owns what or what happened when. Banks keep ledgers, stock exchanges keep ledgers and businesses keep accounting ledgers. What makes a public blockchain unusual is that many independent computers maintain and verify the same record under a common set of rules.
The word “blockchain” comes from the way many networks organize transactions into blocks and link those blocks together in chronological order. Each block contains data that references an earlier block. Changing old data would therefore require changing the later history too, which becomes increasingly difficult once many participants have accepted the chain.
2. Transactions
A blockchain transaction is an instruction that changes the ledger state. On Bitcoin, it may transfer BTC from one set of keys to another. On Ethereum, it may send ETH, move a token, interact with a decentralized exchange or call a smart contract.
Transactions are normally signed with a private key. The signature proves that the person submitting the transaction is authorized to control the relevant assets without revealing the private key itself. Nodes then check whether the transaction follows the protocol rules.
3. Nodes
Nodes are computers running blockchain software. They communicate with one another, relay transactions and blocks, and independently check the rules. A full node stores enough blockchain data to validate the history and current state for itself.
This independent verification is central to decentralization. Instead of trusting a website that says “your balance is 5,” a node can calculate whether that balance is consistent with the blockchain’s accepted transaction history. Not every user needs to operate a node, but the ability to do so reduces dependence on a single information provider.
4. Consensus
If thousands of computers maintain copies of the ledger, they need a method for agreeing on which updates count. This is the job of consensus. Consensus mechanisms define how new blocks are proposed, how participants verify them and how the network chooses between competing versions of history.
Bitcoin uses proof of work, where miners expend computation to propose blocks. Many newer chains use proof of stake, where validators lock or stake assets and participate in block production according to protocol rules. Neither mechanism is “free.” Proof of work relies on external resource costs; proof of stake relies on economic collateral that can be penalized.
5. Why blocks are linked
Blocks normally contain a cryptographic hash of the previous block. A hash is a short fingerprint produced from data. If the underlying data changes, the hash changes. That means altering an earlier block would also break the reference contained in the next block.
This does not make history physically impossible to change. Instead, consensus and economic security make rewriting accepted history increasingly costly. The deeper a transaction is beneath later blocks, the more difficult a successful reorganization generally becomes.
6. Public versus private blockchains
Public blockchains allow broad participation. Anyone can usually inspect the ledger, submit valid transactions and run software to verify the network. Private or permissioned ledgers restrict who can validate or access certain information.
A permissioned blockchain can be useful for organizations that want a shared database with controlled participation. But it does not offer the same censorship resistance or trust model as an open public chain. The word “blockchain” alone therefore tells you little about decentralization.
7. Smart contracts
A smart contract is software deployed to a blockchain that executes according to predefined rules. It can hold assets, calculate values, issue tokens, match trades or enforce conditions without requiring a traditional back-office system to process every action manually.
For example, a decentralized lending protocol may use smart contracts to accept collateral, calculate borrowing limits, charge interest and liquidate positions that fall below required thresholds. The advantage is transparent programmable execution. The risk is that software bugs can become financial bugs.
8. State and virtual machines
Programmable blockchains such as Ethereum maintain a global state: balances, contract storage and other information describing the network at a given moment. Transactions update that state. A virtual machine executes smart-contract instructions in a standardized environment so different nodes can independently reach the same result.
This requirement for deterministic agreement is why blockchain computation can be more expensive than ordinary cloud computing. Every validating node may need to verify the same execution. Blockchains trade efficiency for shared verifiability.
9. Finality
Finality describes the confidence that an accepted transaction will not be reversed. Some networks offer probabilistic finality: the chance of reversal drops as more blocks are added. Others have explicit finality mechanisms where validators vote and finalized blocks are extremely difficult to revert without major protocol violations.
Users should not assume every blockchain has identical settlement guarantees. Confirmation times, validator structure and consensus rules matter, especially for large transfers and bridges.
10. The blockchain trilemma
Blockchain designers often discuss a trade-off between decentralization, security and scalability. A system can optimize all three to some extent, but design choices usually create compromises. Increasing the amount of hardware required to run a validator might improve throughput while reducing the number of people who can realistically verify the chain.
Layer 2 systems attempt to improve scalability by processing activity away from the base chain while using the base chain for settlement or security. This creates another set of trade-offs around data availability, bridges and sequencers.
11. What blockchains are good at
- Maintaining a shared ledger across parties that do not fully trust one another.
- Allowing users to verify balances and transactions independently.
- Moving digitally native assets across an open network.
- Running programmable financial logic through smart contracts.
- Creating transparent settlement records and audit trails.
12. What blockchains are not automatically good at
- Storing large files cheaply.
- Keeping public data secret.
- Processing every workload more efficiently than a centralized database.
- Guaranteeing that external information supplied to a contract is true.
- Eliminating human governance or software bugs.
Many poor blockchain projects begin with the assumption that a blockchain must be the solution. A better question is whether the application genuinely benefits from shared verification, digital ownership or reduced dependence on a central intermediary.
13. Oracles
Blockchains know what happens on their own ledger, but they do not inherently know the price of gold, the outcome of a football match or whether a shipment arrived. Oracles are systems that provide external data to smart contracts.
Oracles create an important trust boundary. A perfectly written lending contract can still fail if its price feed is manipulated. Good protocol design therefore considers data sources, redundancy, update frequency and what happens when data becomes unavailable.
14. Bridges
Different blockchains do not automatically share state. Bridges allow assets or messages to move between networks through various mechanisms such as locking assets on one chain and issuing representations on another.
Bridges have historically been a major source of crypto losses because they may hold large pools of assets and depend on complex smart contracts or validator sets. When using a bridge, users should understand who controls it and what assumptions are required for the transferred asset to remain redeemable.
15. Knowledge check
- Why does a blockchain need consensus?
- What is the role of a full node?
- Why can smart contracts create new risks?
- What is an oracle?
- Why is a blockchain not automatically more efficient than a normal database?
Answers: consensus lets distributed participants agree on valid history; nodes verify rules independently; smart contracts can contain exploitable bugs; an oracle supplies external information; distributed verification deliberately duplicates work in exchange for shared trust and auditability.
16. Practical exercise
Compare Bitcoin and Ethereum. Write down their consensus mechanism, native asset, basic purpose, whether they support general-purpose smart contracts, typical transaction model and how fees are paid. Then choose one transaction on each network and inspect it in a blockchain explorer. Note what information is visible publicly.
17. Key takeaways
A blockchain is not magic. It is a specialized form of shared computing designed to let multiple participants agree on a ledger without depending on one private database. Its strengths—verification, digital ownership and programmable settlement—come with costs in complexity, throughput and user responsibility.
Next lesson: Crypto Wallets: Hot, Cold and Self-Custody Explained →
Educational content only.