Every Bitcoin node follows two sets of rules. One is absolute, enforced by every node on the network. The other is configurable — your node, your choice. This distinction is the key to understanding Bitcoin's security model.
Start Reading ↓On August 15, 1971, one man changed the rules of the world's money.
President Richard Nixon closed the gold window. The United States had promised since Bretton Woods that any dollar could be redeemed for gold at $35 per ounce. That promise was abandoned with a televised address — no vote, no debate, no appeal. The rules of the global monetary system were changed by a single signature.
This was not a bug in the system. It was a feature. The entire architecture of fiat money is designed so that those in power can change the rules when it suits them. Central banks adjust interest rates. Treasuries print more money. Reserve requirements shift. Capital controls appear overnight.
The problem is not that these changes are sometimes necessary. The problem is that the rules have no teeth. They are policies, not laws. They can be rewritten by whoever holds the pen.
"Bitcoin was designed so this can never happen again. Not because it has better promises, but because its rules work differently."
Satoshi Nakamoto didn't just invent digital money. He invented a system where no single entity can change the rules. The rules are enforced by 20,000+ independent nodes running all over the world. To change them, you'd need to convince almost all of those nodes to accept the change — or fork away from them and create your own network.
This is why Bitcoin cannot be Nixon-Shocked. Not because Satoshi was a better person than Nixon. Because the architecture is fundamentally different.
Every Bitcoin node operates by two distinct sets of rules:
Consensus rules are what make Bitcoin, Bitcoin. Every node that follows the consensus rules sees the exact same blockchain — the same transactions, the same balances, the same history. If one node tries to accept a block that violates a consensus rule, every other honest node rejects it immediately. The network self-heals.
Relay policies are how your node decides to handle transactions and peers. Should it accept a transaction with a very low fee? Should it relay transactions that signal Replace-by-Fee? Should it log every connection attempt? These are your choices, and they only affect your node's experience — not the integrity of the blockchain.
Consensus rules keep Bitcoin honest. Relay policies keep it efficient. A misconfigured relay policy makes your node less useful to you. A misapplied consensus rule makes your node not Bitcoin.
The Nixon Shock was possible because fiat money has only policies — and whoever holds power can rewrite them. Bitcoin prevents this by splitting the rulebook into two parts:
The Consensus Rulebook — this cannot be rewritten by anyone. Not a president. Not a central bank. Not a mining pool. Not even Satoshi (who famously stepped away after early stewardship). To change a consensus rule, you must convince the global network of node operators to upgrade — voluntary adoption, not top-down decree.
The Relay Rulebook — this is your personal preferences. This is where you have agency. You decide what transactions to relay, what peers to connect to, what data to keep. This is where the Nixon Shock analogy almost applies — except your relay policies can only affect you.
A central bank can change interest rates and everyone feels it. You can set your node's fee filter to 10 sat/vB and only your node skips low-fee transactions.
"A central bank's policy affects everyone. Your node's relay policy affects only your node. That's the difference between tyranny and sovereignty."
Imagine Alice creates a transaction with a fee of 0.5 sat/vB — below most nodes' relay threshold but technically valid.
Consensus says: "If this transaction is included in a valid block, I will accept it. The signatures check out. The inputs exist. The outputs don't exceed the inputs. It's valid."
Relay says: "I will not forward this transaction to my peers. The fee is too low. It will sit in my mempool until either the fee is bumped or it gets mined by someone with more permissive relay settings."
This is why a transaction can be simultaneously "valid" (all consensus rules pass) and "not relayed" (relay policy says skip). The transaction is not censored — it's just deprioritized. If a miner with low fee thresholds finds it, the transaction gets into a block, and every node on the network must accept it because it satisfies consensus.
This is the magic. Relay policies let the network stay efficient without ever compromising the consensus that makes Bitcoin trustworthy.
This is Part 1 of a 5-part explainer series. Each part builds on the last, taking you from the big idea to hands-on verification.