Regtest

Regtest (regression test mode) is Bitcoin Core's private sandbox: a mode that runs a completely local Bitcoin blockchain with the same basic consensus rules as the public networks, but with total control over block production. There is no peer-to-peer network to join, no waiting for real miners, and no external state at all. You generate blocks instantly on demand, which makes regtest the fastest and most deterministic way to develop and test Bitcoin software — the difference between waiting ten minutes for a confirmation and conjuring one in milliseconds.

How it works

You start a node with the -regtest flag, then call the generatetoaddress RPC to mine blocks whenever your test needs them. Difficulty is trivially low, so block production is effectively instantaneous — the proof-of-work is still real SHA-256, just against a target so easy that a laptop clears it without noticing. Each regtest instance keeps its chain in its own data subdirectory; delete it and you have a factory-fresh blockchain, which gives perfectly repeatable test fixtures. Multiple regtest nodes on one machine can be connected to each other to simulate network behavior — transaction propagation, chain splits, reorganizations — all under scripted control. Deliberately forcing a reorg to prove your software survives one is a standard regtest exercise, and one of the few things no public network lets you do on demand.

The 101-block warm-up

The first 150 regtest blocks each pay a 50 BTC subsidy, mirroring Bitcoin's original schedule (regtest halves quickly thereafter, at block 150 rather than 210,000). Because a coinbase reward must mature for 100 blocks before it can be spent, developers ritually generate 101 blocks at the start of any test session so there is at least one spendable output to build transactions from. The maturity rule being enforced faithfully is the point: regtest is a faithful sandbox for fee logic, mempool behavior, reorg handling, and multi-party protocol flows precisely because it keeps consensus rules intact while surrendering only the block clock.

Why miners and builders should use it

For anyone building against Bitcoin — a payment integration, a wallet, a mining dashboard, a Lightning setup — regtest is where the first hundred iterations should happen. Lightning development leans on it especially hard, since exercising channel opens, force-closes, and penalty transactions requires mining blocks on cue. Mining-adjacent software benefits the same way: pool logic and payout accounting can be exercised against a chain you fully control before touching real hashrate. The sovereignty angle is straightforward: regtest is the entire Bitcoin system, running on your desk, owing nothing to anyone — the logical endpoint of the run-your-own-node ethic, and the cheapest possible classroom. Mistakes cost nothing, secrets never leave the machine, and the chain resets on command.

Regtest gives more control than Signet (a federated public test network) or Testnet (an open proof-of-work one) because there is no external network at all; the usual progression is regtest for development, then a public test network for integration against strangers, then mainnet. See also coinbase maturity for why the 101-block warm-up exists.

Regtest also pairs naturally with automated testing: because the chain is deterministic and resets on demand, it slots directly into CI pipelines, letting a test suite spin up a fresh Bitcoin network, march it through funding, spending, and reorg scenarios, and tear it down in seconds. Framework tooling across languages wraps the RPC calls, so a full wallet integration test reads like ordinary unit-test code. The habit this builds is worth naming: developers who prototype on regtest ship software that has already survived reorgs, mempool evictions, and fee spikes in miniature, while developers who prototype against mainnet tend to discover those events in production. The cheapest place to make Bitcoin mistakes is the network where blocks are free.