The Two Rulebooks · Part 5 of 5
1 2 3 4 5
Part 5 of 5 · No Trust Required

See It Yourself

The Nixon Shock happened in secret, announced on TV. Bitcoin's rules happen in public — every block, every transaction, every node. Here's how to verify them yourself.

🖥️ What You Need

To follow along, you need a running Bitcoin node with bitcoin-cli access. You can run one on:

• A Raspberry Pi (4GB+ RAM, external SSD recommended)
• A VPS (any provider, 2GB+ RAM, 500GB+ storage for full archival)
• Your desktop or laptop (Bitcoin Core runs on Windows, Mac, Linux)

Don't have a node yet? You can still observe some of these using public block explorers like mempool.space or blockstream.info. But nothing beats verifying with your own node.

"Don't trust. Verify. — The most important principle in Bitcoin. Every claim in this series can be checked against a running node."

Experiment 1: Check the Supply Cap

Consensus rule in action: The total supply is capped at 21 million. Let's verify.

1 Get the block count

$ bitcoin-cli getblockcount
888888 (example — yours will differ)

2 Check the block reward at this height

Bitcoin's subsidy halves every 210,000 blocks. Current era (2024+): 3.125 BTC per block.

$ bitcoin-cli getblockchaininfo | grep -i reward
"initialblockreward": 3.12500000 (or similar)

Your node knows the halving schedule because it's a consensus rule — the reward formula is built into every node client.

3 Calculate the circulating supply

You can't create more coins than the subsidy schedule allows. No RPC can return 22 million — the rule is enforced at the protocol level.

$ bitcoin-cli gettxoutsetinfo | grep total_amount
"total_amount": 19.82456789 (roughly 19.8M as of 2026)

The Nixon Shock test: Can any command, any configuration, any software update make this number exceed 21 million? No. The rule is consensus-enforced. Every node would reject a block that violates it.

Experiment 2: See Your Relay Policy in Action

Relay policy in action: Your fee filter decides what transactions enter your mempool.

1 Check your current fee filter

$ bitcoin-cli getmempoolinfo | grep minrelaytxfee
"minrelaytxfee": 0.00001000 (1 sat/vB — the default)

2 See what's in your mempool

$ bitcoin-cli getmempoolinfo
{
"loaded": true,
"size": 4523, # transactions in mempool
"bytes": 12567890, # memory used
"usage": 34567890,
"maxmempool": 300000000, # 300 MB default
"mempoolminfee": 0.00001000
}

The transactions in your mempool passed your node's relay policies. The ones that didn't? They're still valid — they just didn't meet your threshold.

3 Change your fee filter (optional)

Add to bitcoin.conf and restart:

# Raise the bar — only relay transactions with 5+ sat/vB
minrelaytxfee=0.00005000

# Restart your node, then check again:
$ bitcoin-cli getmempoolinfo | grep minrelaytxfee
"minrelaytxfee": 0.00005000

Your node now ignores lower-fee transactions. Your consensus rules haven't changed. Your view of the network has. That's relay policy.

Experiment 3: Check BIP110 Signaling

Consensus change in real time: BIP110 uses version bit 4 for miner signaling. Check which miners are supporting it.

1 Get the latest block

$ bitcoin-cli getbestblockhash
$ bitcoin-cli getblock
{
"hash": "000000000000...",
"height": 888888,
"version": 536870928,
...
}

2 Check if version bit 4 is set

Bit 4 = value 16 (0x10) in the version field. If (version >> 4) & 1 == 1, the miner is signaling BIP110 support.

$ bitcoin-cli getblockheader | grep version
"version": 536870928

# Python check:
$ python3 -c "v=536870928; print('Signaling' if (v>>4)&1 else 'Not signaling')"
Signaling (or Not signaling)

3 Check the last 100 blocks

# Count signaling vs total blocks
$ bitcoin-cli getchaintips
# Or fetch recent blocks and check each version

The percentage of signaling blocks tells you how close BIP110 is to the 55% threshold. This is public, transparent, verifiable — no trust needed.

⬡ Compare with Nixon Shock

The Nixon Shock was announced with zero public signaling. No one voted. No one could verify. BIP110's progress is visible block by block, node by node, anywhere in the world.

🔄 Experiment 4: Test Your RBF Policy

Relay policy choice: Does your node accept transaction replacements?

1 Check your RBF setting

$ bitcoin-cli getmempoolinfo | grep fullrbf
"fullrbf": false

false = only opt-in RBF (default). true = accept all replacements.

2 Change it (optional)

# bitcoin.conf:
mempoolfullrbf=1

# Restart and verify:
$ bitcoin-cli getmempoolinfo | grep fullrbf
"fullrbf": true

Your node now accepts RBF replacements. Your consensus rules haven't changed. The blockchain is identical to a node with RBF disabled. The only difference is in your mempool.

🔑 The Verdict

The Nixon Shock happened because one man could change the rules of money. 20,000+ people spread across every continent run Bitcoin nodes. They all enforce the same consensus rules independently. No one can change those rules without convincing them all.

That's not a policy difference. That's a fundamentally different architecture for money.

Understanding the distinction between consensus rules and relay policies is the difference between trusting an authority and verifying for yourself. Bitcoin gives you the tools to do the latter — you just have to run them.

"The Nixon Shock was the end of trust in money. Bitcoin is the beginning of verification."

Run a node. Verify the rules. Be your own bank.

📚 The Complete Series

You've completed all 5 parts. Here's where to go next:

Part 1
The Two Rulebooks
Part 2
Consensus Rules
Part 3
Relay Policies
Part 4
BIP110 Case Study

Or check out the BIP110 page for the full technical breakdown with node chart, countdown, and deployment parameters.