How are new Bitcoins created?

Man, that Antminer S9 scream brings back some deeply traumatizing memories.

I ran two of those metallic heat-boxes in my tiny apartment garage back in 2017—until my neighbors legitimately complained about what they thought was an industrial vacuum running 24/7. So, trust me. I feel your pain.

You've stumbled onto the exact mental friction point where most casual crypto tourists bail out. They hear "mining" and picture cartoon pickaxes, completely ignoring the sheer mathematical violence happening behind the curtain. But you want the raw, unpolished truth regarding your main question: exactly how are new Bitcoins created?

Let's tear the engine apart.

The Miner Literally Writes Themselves a Check

Your gut instinct was 100% correct. When exploring how are new Bitcoins created, the process literally starts with the winning miner writing themselves a digital check out of absolute thin air. This is the fabled Coinbase transaction (often labeled as Transaction 0 in a block).

Before a miner even starts wildly guessing hashes to solve the current block, they construct a block template. Inside that template, they shove in all the pending mempool transactions they want to process. But right at the absolute top of the list? They inject a brand-new transaction with no existing inputs.

If you query your local node, the "sender" (the vin) is just a string of zeroes. Null. Void. The miner simply dictates, "Pay 3.125 BTC to my personal wallet address."

Crazy, right?

So, Why Not Print a Million BTC?

This leads directly to your second panic point. If the miner is just typing their own paycheck into existence, what stops a greedy pool operator from quietly tacking on a couple of extra zeroes?

Math. Ruthless, unforgiving network consensus.

Here is the gritty reality of how are new Bitcoins created: the creation is a tightly caged permissionless act. Sure, the miner can technically write "Pay me 50,000 BTC" in their block template. They can even successfully hash that block and broadcast it to the global network. But the exact microsecond your humble, quiet Raspberry Pi node receives that block, it runs an automatic background check against the core consensus rules.

Your node calculates the current block height, checks the halving epoch, and expects a block subsidy of exactly 3.125 BTC (plus user fees). If the miner's self-written check asks for 3.12500001 BTC? Your node rejects the entire block outright. Banned. Ignored. Dropped from the memory pool.

The miner just burned thousands of dollars in electricity for literally nothing. The entire network simply laughs and ignores them.

The Core Code: Where the Magic Happens

You wanted the mechanical truth regarding how are new Bitcoins created? I respect that. You need to look straight into the Bitcoin Core source code—specifically a file named validation.cpp.

Inside that file, there is a tiny, beautiful little function called GetBlockSubsidy. It calculates the genesis of those virgin coins using a right bit-shift operation based on the current block height. It starts at 50 BTC and halves every 210,000 blocks. That singular chunk of C++ logic dictates exactly how are new Bitcoins created across the entire planet.

Want to catch this live on your own machine?

• Fire up your terminal.
• Wait for a new block to drop.
• Run: bitcoin-cli getblock <blockhash> 2

Look at the very first transaction in the resulting JSON output. You will see an empty input array and an output array crediting the current block reward to the miner's pool. You are watching virgin, never-before-spent digital bearer assets popping into existence right on your screen.

It feels like witchcraft at first. Eventually, it just feels like beautifully paranoid accounting.

Keep the S9 running for a few more days just to annoy the neighbors—then unplug it before your electricity bill bankrupts you. Let me know if you hit any snags running those node commands!

That S9 noise is basically a rite of passage. Welcome to the club.

The previous poster totally nailed the validation.cpp math. But when folks dive into the rabbit hole of How are new Bitcoins created?, they usually miss a brutal, highly frustrating mechanical trap hidden immediately after that genesis moment. I definitely did.

Back in 2014, I managed to solo-mine a block on some wildly janky GPU rigs. Absolute pure luck. Naturally, I instantly tried to funnel those virgin coins to an exchange.

Rejected. Total dead end.

I panicked—sweating bullets, completely convinced I botched the software setup.

The Radioactive Cooldown Period

Here is a vital piece of the puzzle answering How are new Bitcoins created?: those freshly minted coins are practically radioactive. You cannot spend them immediately.

Bitcoin Core enforces a strict "coinbase maturity" lock. If you deeply analyze How are new Bitcoins created? at the network level, you'll spot that the protocol physically cages Transaction 0 outputs for exactly 100 blocks. Why? Chain reorganizations. Sometimes two miners stumble upon a block simultaneously, creating a temporary network split. If the network orphans your block twenty minutes later, your newly birthed coins literally evaporate into the ether. By forcing a 100-block quarantine, the network guarantees those funds permanently exist before anyone buys a pizza with them.

A Tiny Protocol Quirk to Hunt For

Since you want the raw grit, check out BIP34.

Early on, miners could dump whatever gibberish they wanted in the coinbase input script (Satoshi famously hid a newspaper headline in there). But to prevent duplicate hashes, the rules morphed. Now, to truly grasp How are new Bitcoins created?, you must understand that modern miners are forced to inject the exact current block height directly into that otherwise empty input.

Want to see it?

• Pull up that getblock JSON output again.
• Look inside the vin array for the coinbase hex string.
• Decode that hex payload.

The first few bytes actually translate to the block number itself. It forces absolute cryptographic uniqueness. Without that tiny numerical fingerprint, the network ruthlessly spits the block back in your face.

Keep digging. The rabbit hole goes miles deeper.