Essay · Bitcoin
Bitcoin is an immutable Git repo
Every transaction is a signed commit. The history is chained. And rewriting the past costs more than the whole repo is worth.
The commit message is the transaction
In a normal Git repo, a commit message can say anything — "fix typo," "add tests," "wip." In Bitcoin, the commit message is the transaction itself: who sent what to whom, and how much. The signature attached to it proves you authorized the spend. Anyone can read the ledger and verify the math without trusting you.
The hash chains it all together
Each Git commit points back to its parent through a hash — a fingerprint of the snapshot. Change one line of code and every hash downstream changes. Bitcoin does the same thing with blocks. Each block is a hash of the previous one, so the whole ledger is one long chain of fingerprints. Edit history and the chain breaks.
Where the analogy gets interesting
In Git, whoever owns the repository can rewrite history — force-push, amend, squash. There is a boss. In Bitcoin, there is no boss. Thousands of miners worldwide race to add the next block, and the network accepts whichever chain has the most work behind it. Nobody can quietly rewrite the past because rewriting it would mean out-mining everyone else, which is astronomically expensive.
The master password
When you set up a Bitcoin wallet, it generates a list of twelve or twenty-four random words — your master password. You never type it into a website. You write it down. Lose the physical device and you type those words into a new one; it rebuilds your entire wallet — all your addresses, all your balances. The coins were never stored on the device. They live on the blockchain. The wallet is just the key that unlocks them.
Why this matters for your money
If you keep Bitcoin on an exchange, the exchange holds the keys — and they can freeze, restrict, or hand over your holdings if a regulator or court orders it. That is the difference between having a Bitcoin balance on someone else's server and holding the master password yourself. The analogy holds: a Git repo you don't control is just a copy someone else can delete.