A few weeks ago, if you asked what “trustless” means in Bitcoin, the simple answer would have been: no banks, no middlemen, nobody to trust. It is easy to understand why Bitcoin is described this way. It removes the need for a central authority to maintain the ledger and replaces that role with a network of participants following rules that can be independently verified.
But the more I studied Bitcoin, the less accurate “trustless” seemed as a complete description. Bitcoin doesn’t eliminate trust. It changes what we trust. Instead of trusting one institution to decide which transactions are valid, Bitcoin uses cryptography, consensus rules, Proof of Work, nodes, incentives, and a peer to peer network to establish and verify the state of the system. The important difference is that these assumptions are much more explicit and can often be verified independently.
The Problem Bitcoin Is Actually Solving
One of the fundamental problems Bitcoin addresses is double spending. If the same bitcoin is used in two different transactions, something has to determine which transaction should be accepted. In a traditional financial system, a central authority maintains the ledger and decides which transaction happened first.
Bitcoin needed a way to reach agreement without having one central party controlling the ledger. This is where the blockchain, Proof of Work, nodes, and consensus rules work together. Miners produce blocks, but they do not decide which transactions are valid. Nodes independently verify blocks against Bitcoin’s consensus rules. If a miner includes an invalid transaction, other nodes can reject the block regardless of how much mining work was used to produce it.
This distinction is important because mining power does not give miners control over Bitcoin’s rules. Miners participate in the process of extending the chain, while nodes enforce the rules that determine what is acceptable.
Proof of Work: More Than Just Mining Blocks
Proof of Work is often introduced as a process where miners compete to solve a computational puzzle and receive a reward for finding a block. Its role in Bitcoin’s security goes further than that. Producing Proof of Work requires significant computational resources, while verifying it is comparatively inexpensive. This makes rewriting established history increasingly expensive.
When competing chains exist, nodes use the chain with the most accumulated work as the valid chain under Bitcoin’s consensus rules. This does not make the blockchain impossible to attack. An attacker with enough hash power can attempt to reorganize recent history, but doing so comes with high costs and economic consequences.
Mining therefore involves more than finding blocks. The structure of mining pools, the distribution of hash power, and the incentives of miners can all affect the security of the network. Week 2 also introduced concepts such as selfish mining, which show that mining behavior can become strategic when miners have incentives to deviate from the simplest behavior. This makes mining centralization both an economic and technical consideration rather than simply a question of who owns the machines.
Mining Is Also a Network Problem
Finding a block is only one part of mining. Once a miner finds a block, the block needs to propagate through the Bitcoin network. Bitcoin does not have a central server that immediately distributes the block to every node. Instead, nodes communicate with one another through the peer-to-peer network.
Propagation time matters because miners may temporarily have different views of the latest chain tip. If one miner receives a new block later than another, they may continue working on an older block for some time. Reducing the amount of time required to communicate blocks can therefore improve network efficiency and reduce unnecessary work.
This is where Compact Blocks become useful. When a node already has most of the transactions in a new block, it does not need to receive all of those transactions again. Compact block relay allows nodes to reconstruct much of the block using transaction information they already have, reducing the amount of data that needs to be transmitted.
This shows that Bitcoin’s security is not only about creating blocks. It also depends on how efficiently information moves through the network.
The Bitcoin Network
The peer-to-peer layer introduces another important part of Bitcoin’s security model. Nodes need to discover peers, establish connections, and exchange information about transactions and blocks. There is no single central source from which every node receives the state of the network.
This creates resilience because there is no single server that can simply be shut down, but it also creates possible attack surfaces. One example is an eclipse attack, where an attacker attempts to isolate a node by controlling many of its peer connections. If successful, the attacker can influence the information that the isolated node receives.
This adds another layer to the meaning of trustlessness. A node can independently verify the rules and validity of the information it receives, but it still needs a way to receive information about what is happening across the network. Connectivity, peer selection, network topology, and resistance to attacks therefore matter alongside consensus.
Nodes, Pruned Nodes and What I Got Wrong
There is also an important difference between validation and storage. A full node validates transactions and blocks according to Bitcoin’s consensus rules. A pruned node can perform the same type of validation while deleting older block data that it no longer needs to retain locally.
Pruning therefore does not automatically make a node a weaker validator. The main difference is the amount of historical blockchain data it keeps. Lightweight clients such as SPV wallets make more assumptions because they do not independently validate the entire blockchain in the same way a full node does.
This creates different levels of verification. The question is not simply whether someone “trusts Bitcoin,” but what they are verifying themselves and what assumptions they are making about the system.
SegWit Was More Than Scaling
SegWit became more meaningful when viewed beyond its impact on transaction capacity. One of the important problems it addressed was transaction malleability.
Before SegWit, certain parts of a transaction could be modified without changing what the transaction spent while still changing its transaction ID. By moving signatures outside the traditional transaction commitment, SegWit made transaction IDs more stable.
This had consequences beyond block capacity. More reliable transaction IDs provided an important foundation for protocols built on Bitcoin, including the Lightning Network.
A useful lesson here is that a change to a base-layer protocol can enable functionality at higher layers without requiring the base layer itself to process every interaction directly.
Script Changed How Bitcoin Transactions Work
Bitcoin transactions are more than instructions to send a specific amount from one person to another. They define conditions that must be satisfied before the associated coins can be spent.
Bitcoin Script is the small programming language used to express these spending conditions. This means that controlling bitcoin is fundamentally about being able to satisfy the conditions required by the output holding those coins.
This also explains how Bitcoin can support different spending arrangements without requiring a central authority to approve them. The conditions are defined by the protocol and enforced by the nodes validating transactions.
From Script to Miniscript and Taproot
Miniscript builds on Bitcoin Script by providing a structured way to express spending policies. This makes complex scripts easier to analyse, compose, and reason about.
Taproot extends Bitcoin’s scripting and signature capabilities further. Alongside Taproot, Schnorr signatures introduce properties that can make certain multi-signature and transaction constructions more efficient and flexible.
These developments demonstrate how Bitcoin can evolve while maintaining its basic model of independently verifiable rules. Rather than replacing decentralised verification with a central authority, protocol improvements expand what can be built within the existing system.
Wallets Are More Than Private Keys
HD wallets provide another example of how Bitcoin’s different components fit together. A wallet is not simply a container where private keys are stored. Hierarchical deterministic wallets can derive multiple keys and addresses from a common seed, making key management and backup more practical.
Looking at wallets alongside transactions, Script, nodes, and mining makes it clear that Bitcoin is not one isolated technology. It is a collection of systems that interact with one another: cryptography protects ownership, Script defines spending conditions, nodes enforce consensus rules, miners contribute Proof of Work, and the P2P network distributes information.
Understanding these connections is more useful than treating each concept as an isolated definition.
The Trust Didn’t Disappear; It Became More Specific
Across these two weeks, the idea of “trustless” became more precise. Bitcoin still depends on assumptions. There are cryptographic assumptions, assumptions about the security of proof of work, assumptions about network connectivity, assumptions about software, and economic assumptions about the incentives of participants.
The difference is that Bitcoin does not require all participants to place their trust in one institution. Many of the system’s rules can be independently verified, and different participants can choose how much of the system they want to verify themselves.
Instead of:
“Trust this institution because it says the ledger is correct.”
the model becomes closer to:
“Here are the rules. Verify them yourself.”
That distinction is at the center of Bitcoin’s approach to trust.
My Biggest Takeaway
Across 2 weeks, my understanding of Bitcoin shifted from seeing it mainly as a system that removes trust to seeing it as a system that reduces, distributes, and makes trust more explicit. Week 1 gave me the foundation: double spending, Proof of Work, nodes, mining, consensus, and SegWit. I learned that miners produce blocks, but nodes enforce the rules, and that Bitcoin’s security does not depend on one single mechanism.
Week 2 expanded that picture by showing what happens around that consensus. Mining is not just about finding blocks; block propagation, mining pools, incentives, and strategic behaviour also affect the network. The P2P layer showed me that nodes need to discover and communicate with peers, while attacks such as eclipse attacks demonstrate that network connectivity is another part of Bitcoin’s security model. Script and wallets added another layer by showing how Bitcoin defines spending conditions and manages keys, while Miniscript, Taproot, and Schnorr signatures show how the protocol can evolve without giving up independent verification.
The biggest change has been in the questions I ask when learning a new Bitcoin concept. Instead of only asking “What is this?”, I now try to ask “What problem does this solve, how does it work, and what new assumptions or problems does it introduce?” Proof of Work establishes a costly history, but how does that history propagate? Nodes validate the rules, but how do they receive information from the network? Script allows programmable spending conditions, but how can those conditions be expressed safely?
I started this journey thinking Bitcoin was about removing trust. A more accurate way to describe it now is that Bitcoin reduces the amount of trust required and replaces much of that trust with verifiable rules, cryptography, and economic incentives. Its security comes from several layers working together:
Cryptography → Transactions → Script → Nodes → P2P Network → Mining → Proof of Work → Economic Incentives
Each layer contributes something different, and the assumptions at one layer can affect the others. Bitcoin therefore does not eliminate trust completely. It changes where trust is placed, reduces the need to trust a central party, and makes many of the remaining assumptions visible enough to question and verify.
And maybe that is what “trustless” really means in Bitcoin:
not trusting nobody, but trusting fewer things and being able to verify more of them yourself.