Developers use it to exercise nodes, wallets, transactions, mining and network integrations against public peers without risking real BTC; each testnet has its own genesis block, chainstate and network parameters.
TBTC is disposable test material and is not intended to carry a market price or investment meaning. Faucets or mining distribute coins, but scarcity does not turn them into BTC and balances cannot move to mainnet.
Mainnet, Testnet3, Testnet4, Signet and Regtest have distinct genesis blocks and disjoint UTXO sets. Network magic, ports, peers and data subdirectories stop a node from accepting another chain's blocks.
Testnet3 ran from 2011, and its height, coin distribution and minimum-difficulty rule gradually harmed usability. Repeated block storms and trading of TBTC contradicted the goal of a cheap, unstable testing resource.
BIP 94 created Testnet4 with a new genesis block, block-storm and time-warp mitigations, and mainnet soft forks active from genesis. Bitcoin Core selects it with -testnet4, while retaining a twenty-minute difficulty exception.
BIP 95 proposes Testnet5 without the minimum-difficulty exception and with BIP 54 rules from block one. On 30 August 2026 it is Draft, its parameters are incomplete, and it must not be presented as a deployed Bitcoin Core network.
A public testnet has low variable hashrate, outside miners, reorgs, empty mempools and unreliable faucets. That exposes integration faults but does not reproduce mainnet fee markets, liquidity, propagation or economic finality.
Testnet4 is a permissionless public proof-of-work chain. Signet requires blocks to satisfy a signing challenge for more predictable public testing; Regtest is a private local chain where the test creates blocks on demand.
Some testing networks share address prefixes such as tb1, so a string alone may not identify one chain. Use separate wallet files, seeds and descriptors; reusing keys links tests and can damage privacy under a bad configuration.
Bitcoin Core separates testnet3, testnet4, signet and regtest data directories. After launch, check getblockchaininfo.chain, the genesis hash, peers and height; configuration uses [test] for Testnet3 and [testnet4] for Testnet4.
Define network, client version, expected activations, coin source, confirmation target and reorg tolerance. Test receipt, change, RBF or CPFP, restart, wallet recovery, RPC errors and wrong-network rejection, then repeat on Signet or Regtest when useful. BIP 94 — Testnet 4 · BIP 95 — Testnet 5 (Draft) · Bitcoin Core 28.0 — Testnet4 support · Bitcoin Core — chain parameters · Bitcoin Core — Signet, testnet and regtest modes · Bitcoin Core — bitcoin.conf network sections · Bitcoin Core — chain-specific data directories · Bitcoin Core 30.0 — getblockchaininfo
For the clearest picture, read this entry together with Bitcoin Core, Signet, Mining, Bitcoin wallet, Bitcoin, Full Node. The reverse links also lead from Sidechain, Liquid Network, Signet.