Johnny

Picture a high school rowing team picking who sits in the stroke seat. That seat sets the pace for the whole boat, so it matters who gets it.

One coach runs a test every Monday at dawn. Every rower pulls two thousand meters on a rowing machine, and the fastest time takes the seat for the week. Last week's win counts for nothing. Next Monday, everyone pulls again.

Another coach gives the seat to the rower whose family gave the most to the booster club. The kid in that seat gets noticed by college scouts, which brings a scholarship, which frees up more money for the booster club next year. The seat pays for itself.

Bitcoin works like the first coach. Miners earn the right to add the next block of transactions by spending real electricity on specialized machines. That is called proof of work. The cost comes from outside the system, and it has to be paid again for every block. Nobody can coast on yesterday's power bill.

Many other networks work like the second coach. They use proof of stake, where the people who lock up the most coins get picked most often to add blocks, and they earn new coins for doing it. Those new coins can be locked up again. The say you have tomorrow grows out of the say you hold today.

I have run miners myself. The power bill shows up every month whether I find a block or not. Control has to be bought again and again from the physical world.

The other side has a fair case. Proof of stake uses a tiny fraction of the energy. Mining also has its own snowball, since large miners buy machines in bulk and get cheaper power deals than a small miner like me. A big enough operation can grow its share too.

How would I know I am wrong? If, over many years, the share of mining held by the top few pools grew faster than the share of staking held by the top few holders, the rowing story would stop holding up. I would also change my mind if a miner could keep control without spending fresh power on each block.

Until then I trust the Monday morning test. Bitcoin asks every miner to prove it again, about every ten minutes, and I keep a node running at home to check that they did.

if this made the Monday test click for you, Zap ⚡

Picture a family pumpkin patch that is open six weeks a year. Every October, cars line the gravel road, kids pick their pumpkins, and parents pay at a folding table by the barn. Then the gate closes and the bills start. Seed in the winter. Tractor fuel in the spring. The land lease in the summer. Every one of those bills is due in dollars.

Now picture that family deciding to take bitcoin at the folding table. Taking the payment is the easy part. A phone shows a code, a customer scans it, and the money arrives in seconds over Lightning, a payment network built on top of Bitcoin for small, fast payments.

After the gate closes, the family faces a second choice. Do they keep the bitcoin they took in, or swap it for dollars that same night?

I see two different decisions hiding inside one. Accepting bitcoin is a checkout choice. Holding bitcoin is a savings choice. A merchant can say yes to the first and no to the second, and plenty of them should. The price of bitcoin can move a lot in a few months. That swing is called volatility. A family that needs a fixed number of dollars for a lease in July cannot plan around a number that could be much higher or much lower by then.

So many shops that accept bitcoin convert some or all of it right away. Some keep a small slice as savings and convert the rest. That split is an ordinary business decision, the same way a farmer decides how much grain to sell at harvest and how much to store in the bin.

The other side has a fair point. If a merchant converts every payment to dollars the same night, what did bitcoin add? The customer could have tapped a card. Fees can be lower, and there are no chargebacks, which are payments a card company pulls back weeks after the sale. A skeptic can call that a small edge and point out that customers rarely ask to pay this way.

How would I know I am wrong? Picture merchants who were offered instant conversion, lower fees and no chargebacks, and who still turned bitcoin down at the same rate as before. If I saw that, I would stop telling shop owners that the checkout is the easy part.

Until then I keep the two questions apart. I have held bitcoin since 2015, and I still think a pumpkin patch owner should first ask how the lease gets paid in July.

if this split one choice into two for you, Zap ⚡

Picture a dozen food trucks parked on one empty lot every night. Each owner buys their own food, pays their own cook and keeps what they sell. The lot has one shared thing: a power hookup that every truck plugs into. It breaks sometimes, and somebody has to fix it.

One night a proposal goes around. Each truck hands over one dollar in ten to pay a person who keeps the hookup running. It sounds fair. The hookup matters to everyone.

Before I decide if the plan is good, I ask a simpler question. Who takes home less? The busy truck shrugs. The truck that barely covers its gas feels that dime first and starts looking at another lot.

Bitcoin has the same shape. Miners are the people who run machines that secure the network. About every ten minutes one miner wins the right to add the next block, a page of new transactions. The winner is paid two ways. The block subsidy is new bitcoin created with each block, 3.125 bitcoin today. Fees are what you pay to get your transaction included.

Every so often someone proposes taking a slice of that reward and sending it somewhere else, often to fund the developers who maintain Bitcoin's code. The code is the shared hookup. Everyone plugs into it. Somebody has to keep it running.

Here is where I land. A proposal like that is a question about who gets paid before it is a question about code. The slice comes out of miner pay. Miners with cheap power barely notice. Miners on thin margins notice first, and some of them switch off. And a developer paid by a fixed slice of every block now has a paymaster, which changes who they answer to.

The other side has a strong case. Open source work is underfunded. Volunteers burn out. Grants come and go with the mood of donors. A steady, automatic slice could fund careful work for decades, and a network that cannot pay for its own upkeep carries a risk of its own.

So how would I know I am wrong? Picture a network that paid its developers from block rewards for years. Hashpower (the total computing work miners point at the network) stayed steady, and small miners stayed on. Those developers still said no to the people funding them. If I saw that, I would change my mind.

Until then I read these proposals the way I would read the food truck plan. I look at who hands over the dime before I look at how the hookup gets fixed. I have watched miners since 2015 and I mine today, and the pay line is where I start.

if this made you ask who pays before you read the plan, Zap ⚡

Picture an apartment complex with two buildings. Your unit has thick walls and blackout curtains. Your friend's unit across the courtyard is just as private. The neighbors see none of what happens inside either one.

Now you want to hand your friend a heavy basket of laundry. The only path between the two buildings runs through the shared laundry room, and the manager keeps a clipboard by the door. Everyone signs in with a unit number, a time and how many loads. At 7:02 the sheet says unit 4B dropped off three loads. At 7:05 it says unit 9A picked up three loads. The manager never looked inside a basket and still knows what moved and who it went to.

That clipboard is how I think about moving money between two blockchains. A blockchain is a shared record of who owns what. A bridge is a service that locks coins on one chain and issues a matching claim on the other. Each chain can have strong privacy on its own. The bridge sits in the middle and sees the amount going in, the amount coming out and the minutes between them. Line those up and the private path turns into a public one.

Privacy belongs to the whole trip from start to finish. The weakest step sets the level for everything after it.

Bridges carry a second problem. The locked coins sit in one pile, and one pile makes a big target. In 2022 a single bridge hack drained more than $600 million. The pile was the prize.

The other side deserves a fair hearing. Engineers have worked on this for years. Builders say bridges get safer every year and that networks will soon talk to each other directly, with no middle pile and no clipboard. If that arrives, much of this worry goes away.

I would change my mind if transfers between networks stayed private and safe at real volume, and bridge losses kept falling year after year. I am watching for that and I have not seen it yet.

Until then I keep things simple. I have held bitcoin since 2015, and my savings stay on one network where I hold the keys. Every hop to another chain is one more clipboard by the door.

if this made you look twice at the clipboard by the door, Zap ⚡