Skip to main content

Signet | Bitcoin Glossary | Mapping Bitcoin

Signet

Desarrollo

Also known as: BIP325

A Bitcoin test network where block creation is controlled by a set of authorized signers rather than permissionless mining. Signet provides a more stable and predictable testing environment than testnet, with consistent block times and no spam disruptions.

Overview

Signet (BIP325) is a Bitcoin test network designed to provide a more reliable and predictable testing environment than the traditional testnet. Instead of using permissionless proof-of-work mining (where anyone can mine blocks), signet requires blocks to be signed by a set of authorized keys. This prevents the erratic block times, spam attacks, and chain reorganizations that frequently plague testnet.

Signet vs. Testnet vs. Regtest

┌──────────────┬──────────────┬──────────────┬──────────────┐
│              │   Testnet    │   Signet     │   Regtest    │
├──────────────┼──────────────┼──────────────┼──────────────┤
│ Block        │ PoW (anyone  │ Signed by    │ On-demand    │
│ production   │ can mine)    │ authorized   │ (instant)    │
│              │              │ signers      │              │
├──────────────┼──────────────┼──────────────┼──────────────┤
│ Block times  │ Erratic      │ Consistent   │ Instant      │
│              │ (0s to hours)│ (~10 min)    │              │
├──────────────┼──────────────┼──────────────┼──────────────┤
│ Network      │ Public       │ Public       │ Private      │
│              │              │ (or custom)  │ (local)      │
├──────────────┼──────────────┼──────────────┼──────────────┤
│ Stability    │ Low (reorgs, │ High         │ Full control │
│              │ spam)        │              │              │
├──────────────┼──────────────┼──────────────┼──────────────┤
│ Coins from   │ Faucets      │ Faucets      │ Self-mined   │
├──────────────┼──────────────┼──────────────┼──────────────┤
│ Best for     │ Public       │ Realistic    │ Local dev    │
│              │ testing      │ integration  │ & unit tests │
│              │              │ testing      │              │
└──────────────┴──────────────┴──────────────┴──────────────┘

How Signet Works

In a signet network, each block must include a valid signature from the designated signing key(s) in addition to meeting standard block validity rules. The signer(s) produce blocks at a regular cadence (approximately every 10 minutes on the default signet), closely mimicking mainnet behavior.

Default Signet

Bitcoin Core includes a default signet network operated by Bitcoin Core developers. This network:

  • Produces blocks approximately every 10 minutes
  • Maintains a stable, continuous chain without disruptions
  • Provides faucets for obtaining test coins
  • Supports all protocol features including SegWit and Taproot

Custom Signets

One of signet's key features is the ability to create custom signet networks with your own signing keys. This is valuable for:

  • Corporate testing — Companies can run private signet networks for internal development
  • Feature testing — Developers can deploy experimental consensus changes on a custom signet before proposing them for mainnet
  • Education — Instructors can run controlled signet environments for workshops and courses

Problems Signet Solves

Testnet has historically suffered from several issues that make it unreliable for development:

  • Block time instability — Difficulty resets can cause hundreds of blocks to be mined in minutes, followed by long gaps
  • Chain reorganizations — Malicious miners can cause deep reorgs, disrupting testing
  • Coin spam — Testnet coins occasionally develop market value, leading to hoarding and faucet exhaustion
  • Resource waste — PoW mining on testnet consumes energy for no purpose

Signet eliminates all of these problems by using signature-based block production.

Common Misconception

Signet's centralized block production does not mean it is "less valid" for testing than testnet. The signing requirement only controls block creation — all other protocol rules (transaction validation, script execution, consensus rules) are identical to mainnet. The controlled block production is a feature, not a limitation, because it provides the stability developers need to test reliably.