Tools/Explorers

Bitcoin Test Networks Compared: Testnet4, Signet, and Regtest

Compare Bitcoin test networks by reliability, faucet availability, block production, and suitability for different testing needs.

Spark Team

Bitcoin Test Network Overview

Bitcoin developers have three test networks available for building and validating software: Testnet4, Signet, and Regtest. Each serves a different stage of the development lifecycle, from local unit tests to multi-party integration testing on a shared public chain. Choosing the wrong network wastes time: Regtest cannot simulate network latency, Testnet4 may produce blocks unpredictably, and Signet requires trusting a block signer.

The following table provides a high-level comparison. Detailed breakdowns of each network follow below.

FeatureTestnet4Signet (Default)Custom SignetRegtest
SpecificationBIP 94BIP 325BIP 325Built-in
Block productionProof of workSigned by authoritySigned by your keysOn demand (local)
Block interval~10 min (variable)~10 min (consistent)ConfigurableInstant
Network typePublic, permissionlessPublic, permissionedPrivate or publicLocal only
SegWitActive from genesisActive from genesisActive from genesisConfigurable activation
TaprootActive from genesisActive from genesisActive from genesisConfigurable activation
Coin supplyMined (50 BTC reward)Faucet-distributedSelf-mined/faucetSelf-mined
Faucet availabilityLimited, often scarceOne claim/day per IPYou control supplyN/A (mine locally)
Default P2P port48333383333833318444
Default RPC port48332383323833218443
Bitcoin Core flag-testnet4-signet-signet -signetchallenge=...-regtest
Added in Corev28.0 (Oct 2024)v0.21.0 (Jan 2021)v0.21.0 (Jan 2021)v0.9.0 (2014)

For a deeper look at running a full node on each of these networks, see our Bitcoin node software comparison.

Testnet4: The Public Proof-of-Work Test Chain

Testnet4 (BIP 94) is the current public Bitcoin testnet. It was introduced in Bitcoin Core v28.0 (October 2024) as a replacement for Testnet3, which had become unusable due to a difficulty adjustment exploit. Testnet4 follows mainnet consensus rules with three exceptions: the 20-minute minimum-difficulty rule is preserved for CPU mining, the difficulty adjustment calculation uses the first block of the previous period (instead of the last) to prevent block storms, and blocks at period boundaries must have timestamps no more than 600 seconds before the previous block to close the time-warp attack vector.

Because Testnet4 uses real proof of work, it is the closest public analogue to mainnet. Block intervals average around 10 minutes but can vary significantly. The block reward starts at 50 tBTC and follows the same halving schedule as mainnet. All soft forks through Taproot are active from the genesis block.

Testnet4 faucets exist but coin supply is often scarce. Most mined coins stay with miners rather than flowing to public faucets, and faucet operators rate-limit claims to prevent abuse. Plan for delays when acquiring test coins, or consider Signet or Regtest if you need immediate access.

Signet: Predictable Signed Blocks

Signet (BIP 325) replaces proof-of-work block production with cryptographic signatures from a designated authority. Blocks are only valid if they include a signature satisfying the network's challenge script. This eliminates the block storms, difficulty manipulation, and chain reorganizations that plague proof-of-work test networks.

The default Signet, maintained by Bitcoin Core contributors, produces blocks approximately every 10 minutes using a 1-of-2 multisig challenge. All protocol features including SegWit and Taproot are active from genesis. The default Signet faucet typically limits claims to one per IP address per day, which provides enough coins for most development workflows without enabling abuse.

Custom Signets

Any team can launch a private Signet by generating signing keys, defining a challenge script (even a simple OP_TRUE for internal use), and passing it to bitcoind with the -signetchallenge flag. Custom Signets allow you to control block intervals (some teams use 30-second intervals for faster CI pipelines), restrict who can mine, and run isolated environments for protocol-level experiments. The genesis block is shared across all Signets, but the network magic is derived from the SHA-256d hash of your challenge script, so custom Signets are automatically isolated from the default network.

Regtest: Local On-Demand Blocks

Regtest (regression test mode) is a fully local chain with no network peers. Blocks are generated on demand using bitcoin-cli generatetoaddress, with near-zero difficulty so each block is produced instantly. This makes Regtest ideal for unit tests, automated test suites, and any workflow where you need deterministic control over block timing.

Regtest follows mainnet consensus rules but allows configurable soft fork activation heights. You can test pre-SegWit behavior, SegWit-only code, or Taproot spending paths by adjusting activation parameters. Mined coinbase outputs require 100 confirmations before they can be spent (the standard coinbase maturity rule), so generate at least 101 blocks after mining to have spendable funds.

Because Regtest runs entirely locally, it cannot simulate network propagation delays, peer discovery, or multi-node gossip. For testing that requires realistic network conditions, use Signet or Testnet4.

Why Was Testnet3 Deprecated?

Testnet3 suffered from a difficulty-reset exploit that allowed miners to flood the chain with blocks. The 20-minute minimum-difficulty exception, combined with how difficulty adjustment calculated its base from the last block of the retarget period, meant an attacker could manipulate timestamps to reset difficulty to minimum. In practice, this produced "block storms" where years' worth of blocks were mined in a matter of weeks.

The block reward had also dropped to approximately 0.014 tBTC through halvings, making it ineffective at distributing test coins. Secondary markets emerged where people sold testnet coins for real money, defeating the purpose of a valueless test chain. Bitcoin developer Jameson Lopp's 2024 mailing-list post catalyzed the decision to create Testnet4 via BIP 94. Bitcoin Core v28.0 officially deprecated Testnet3, and later releases removed support for it entirely.

Lightning Network Compatibility

Testing Lightning channels and payment routing requires a test network that supports SegWit (required for Lightning's commitment transaction format) and ideally Taproot (for simple Taproot channels). All three networks qualify, but ecosystem support differs.

ImplementationTestnet4SignetRegtest
LNDSupported (merged early 2025)Supported (since 2021)Supported
Core Lightning (CLN)Check latest releaseSupported (since 2019)Supported
EclairCheck latest releaseSupported (since 2022)Supported
LDKSupportedSupportedSupported

Signet has the most mature Lightning testing ecosystem. LND, CLN, and Eclair all have established Signet support, with active peers available for channel and routing tests. Testnet4 Lightning support is newer, with LND merging support in early 2025 and LDK also supporting it. Regtest is universally supported but limited to local multi-node setups without real network conditions. For more on Lightning implementation differences, see our Lightning implementation comparison.

Which Network for Which Test?

The right network depends on what you are testing. The following decision table maps common development tasks to the best-fit network.

Use CaseBest NetworkWhy
Unit tests and CI pipelinesRegtestInstant blocks, deterministic, no external dependencies
Integration tests (single developer)Regtest or Custom SignetFull control over block timing and coin supply
Multi-party integration testsDefault SignetShared public chain with predictable blocks, existing peers
Demo applicationsDefault SignetStable block times, reliable faucet, mainnet-like behavior
Load testing and stress testingCustom Signet or RegtestConfigurable block intervals (30s or faster), controlled environment
Mining software testingTestnet4Real proof of work with difficulty adjustment
Adversarial condition testingTestnet4Permissionless mining, potential reorgs, realistic fee market
Lightning channel testingSignetExisting Lightning peers, predictable confirmations
Taproot script-path testingAny (all support Taproot)Regtest for rapid iteration, Signet for multi-party
Wallet UX testingDefault SignetRealistic block times without Testnet4's reliability issues

Faucet Availability and Coin Acquisition

Acquiring test coins is one of the most common pain points in Bitcoin development. Each network handles coin distribution differently.

Testnet4 coins:

  • Block reward is 50 tBTC, same as mainnet at launch
  • Public faucets exist but supply is often constrained
  • Faucet operators rate-limit claims to prevent hoarding
  • You can CPU-mine blocks using the 20-minute minimum-difficulty rule

Signet coins (default):

  • Distributed through the official faucet, typically one claim per IP per day
  • Supply is controlled by the Signet operators, preventing inflation abuse
  • Coins have no secondary market value, keeping the network focused on development
  • A proof-of-work-based Signet faucet concept has been proposed for more decentralized distribution

Regtest coins:

  • Mine your own with generatetoaddress
  • No faucet needed: you control the entire chain
  • Remember the 100-block coinbase maturity requirement

Running Spark SDK on Test Networks

Developers building on Spark can test against Bitcoin test networks to validate wallet integration, VTXO management, and stablecoin transfers before deploying to mainnet. Spark's architecture operates as a Bitcoin Layer 2, so test environments map to the underlying Bitcoin network. Check the Spark documentation for the latest on which test networks are supported and how to configure the SDK for testnet or Signet. For a broader look at Bitcoin development tooling, see our Bitcoin dev kit comparison.

Frequently Asked Questions

Why was Bitcoin Testnet3 deprecated?

Testnet3 had a difficulty-reset exploit that let miners flood the chain with millions of blocks in short bursts ("block storms"). The difficulty adjustment algorithm based its calculation on the last block of each retarget period, allowing timestamp manipulation to reset difficulty to minimum. The block reward had also halved down to approximately 0.014 tBTC, making coin distribution ineffective. Secondary markets for testnet coins emerged, undermining the network's purpose. BIP 94 (Testnet4) fixed these issues by basing difficulty on the first block of each period and adding a time-warp guard.

Can I run Spark SDK on Signet?

Spark is a Bitcoin Layer 2 protocol, and its SDK can be configured for different Bitcoin networks. Check the Spark documentation for the latest supported test environments. Signet is generally a good fit for testing Layer 2 protocols because of its predictable block times and stable chain state. The Spark SDK integration guide covers wallet setup in detail.

What is the difference between Signet and Testnet4?

Testnet4 uses real proof of work with permissionless mining, making it the most mainnet-like public test network. Signet uses signed blocks from a designated authority, providing predictable block intervals and eliminating chain instability. Use Testnet4 when you need to test under adversarial mining conditions or validate mining software. Use Signet when you need reliable block production for application development, CI pipelines, or Lightning channel testing.

How do I get Bitcoin testnet coins from a faucet?

For Testnet4, search for active Testnet4 faucets and submit your testnet address (prefix tb1 for bech32 addresses). Expect rate limits and possible delays. For the default Signet, the official faucet allows approximately one claim per IP address per day. For Regtest, no faucet is needed: run bitcoin-cli -regtest generatetoaddress 101 <your_address> to mine blocks and obtain spendable coins.

Does Testnet4 support Taproot and SegWit?

Yes. Testnet4 activates all mainnet soft forks, including SegWit and Taproot, from the genesis block. This means you can test Tapscript opcodes, Schnorr signatures, and key-path or script-path spends immediately without waiting for activation heights.

Can I run a custom Signet for my team?

Yes. Generate a signing key, define a challenge script (a simple 1-of-1 multisig or even OP_TRUE), and launch bitcoind with -signet -signetchallenge=<hex>. The network magic is automatically derived from your challenge script's hash, isolating your custom Signet from the default network. You can configure block intervals, control coin distribution, and restrict participation to your team. This is especially useful for CI pipelines, QA environments, and protocol experiments.

Which test network should I use for Lightning development?

The default Signet is the best choice for most Lightning development. All major implementations (LND, CLN, Eclair, LDK) support Signet, and there is an existing ecosystem of Signet Lightning peers for channel and routing tests. Regtest works well for local multi-node setups where you control all nodes. Testnet4 Lightning support is still maturing, with fewer active peers. For a detailed comparison of Lightning implementations, see our Testnet4 and Signet developer guide.

This tool is for informational purposes only and does not constitute financial or technical advice. Network specifications, faucet availability, and implementation support change as Bitcoin Core and Lightning implementations release new versions. Always verify current details against official documentation and BIP specifications before making architectural decisions.

Build with Spark

Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.

Read the docs →