Tools/Explorers

Custom Bitcoin Signet Network Comparison

Compare custom Bitcoin signet networks by block time, faucet reliability, Lightning support, explorer availability, and developer use cases.

Spark Team

Custom Signet Networks at a Glance

Bitcoin's signet protocol (BIP 325) lets anyone run a test network where blocks are signed by one or more designated keys rather than mined competitively. The default signet, maintained by Bitcoin Core contributor Karl-Johan Alm, mirrors mainnet's ~10-minute block time and serves as the standard public test chain. Custom signets modify the challenge script, block interval, or pre-deployed infrastructure to suit specific development workflows.

The table below compares the most widely used signet networks. Each derives its own network magic from its challenge, so nodes connect only to peers on the same chain.

NetworkBlock IntervalOperatorFaucetExplorerLightning InfraPrimary Use Case
Default Signet~10 minKallewoof (Bitcoin Core)signetfaucet.commempool.space/signetCommunity-run nodesGeneral wallet and protocol testing
Mutinynet~30 secMutiny teamfaucet.mutinynet.commutinynet.com (mempool.space fork)Pre-deployed LND nodes, Voltage LSP, rapid gossip syncLightning, Fedimint, Cashu, Ark testing
Bitcoin Inquisition~10 minAJ Towns (Bitcoin Core)Default signet faucet (shared chain)mempool.space/signetNone dedicatedSoft fork testing (OP_CAT, CTV, APO)
Catnet~10 minsCrypt / communityVariesLimitedNoneOP_CAT-specific contract experiments

For a broader comparison of test networks (including testnet4 and regtest), see our testnet vs signet vs regtest guide and the testnet4 and signet developer guide.

Default Signet

The default signet ships with Bitcoin Core (enabled via signet=1 in bitcoin.conf) and requires no additional configuration. Its challenge script is a single public key controlled by Kallewoof, who signs blocks at approximately 10-minute intervals to replicate mainnet's cadence. This makes the default signet the most stable and predictable public test environment: blocks arrive on schedule, there is no griefing or hash-rate volatility, and the chain never reorgs unexpectedly.

The default signet faucet at signetfaucet.com dispenses roughly 1,000 to 10,000 satoshis per request, with daily limits per IP address and per receiving address. Mempool.space hosts a full block explorer for the default signet at mempool.space/signet, providing transaction lookup, mempool visualization, and fee-rate charts.

Mutinynet

Mutinynet is a custom signet created by the Mutiny Wallet team with 30-second block intervals. The faster block time makes it the preferred network for testing Lightning channels, Fedimint federations, Cashu mints, and Ark transactions, where waiting 10 minutes per on-chain confirmation would slow iteration dramatically.

Mutinynet's infrastructure includes a mempool.space-based block explorer, an Esplora API endpoint at mutinynet.com/api, a rapid gossip sync server for fast Lightning graph bootstrapping, pre-deployed LND nodes, and the Voltage LSP for inbound liquidity. The faucet at faucet.mutinynet.com supports on-chain, Lightning, Fedimint, Cashu, and Ark payouts.

Running your own Mutinynet full node requires building a modified Bitcoin Core fork that supports the -signetblocktime flag. Standard Bitcoin Core does not accept custom block time parameters for signet. Pull requests to add this flag have been opened for btcd and LND, but the feature is not yet part of upstream releases. Most developers connect through the hosted Esplora endpoint rather than syncing a local node.

Note: Mutiny Wallet (the Lightning wallet app) shut down on December 31, 2024. The Mutinynet signet network continues to operate independently and remains available for developer testing.

Bitcoin Inquisition

Bitcoin Inquisition is not a separate network: it is a modified Bitcoin Core client that runs on the default signet and enforces proposed consensus changes that have not yet been activated on mainnet. Maintained by AJ Towns, it branches from stable Core releases and adds support for proposals including OP_CAT (BIP 347), CTV (BIP 119), and APO (BIP 118).

Inquisition 25.2 activated OP_CAT enforcement on signet in April/May 2024, and Inquisition 29.2 (released February 2026) continues active testing. Transactions that use these new opcodes are visible only to Inquisition nodes until confirmed in a block, at which point they appear on standard signet explorers as well. Because Inquisition shares the default signet chain, developers can use the same faucets and explorers: they just need to run the Inquisition client to create and validate experimental transactions.

Setup and Sync Requirements

Initial sync time and disk usage vary significantly across networks. Custom signets with faster block times accumulate more blocks but typically carry lighter transaction loads. The following table provides approximate requirements based on publicly available data.

NetworkNode SoftwareApprox. Chain SizeInitial Sync TimeCustom Build Required
Default SignetBitcoin Core (standard)~2 GB (prunable)Minutes to low tens of minutesNo
MutinynetModified Bitcoin Core fork~5-10 GB (30s blocks accumulate faster)30-60 min (more blocks to validate)Yes (signetblocktime fork)
Bitcoin InquisitionInquisition client (Core fork)Same as default signetSame as default signetYes (Inquisition build)
Regtest (for comparison)Bitcoin Core (standard)Negligible (local only)Instant (no sync)No

All signet chains can be pruned with the standard prune=N configuration, keeping only the most recent N megabytes of block data. For the default signet, pruned storage can be as low as 550 MB. See our node software comparison for details on client options.

When to Use a Custom Signet vs Regtest

Regtest and custom signets solve different problems. The choice depends on what stage of development you are in and whether you need interaction with other parties.

  • Regtest is best for unit testing, rapid prototyping, and any workflow where you control all participants. You generate blocks on demand with bitcoin-cli -regtest generatetoaddress, so there is zero wait time. The tradeoff: regtest is entirely local, with no public explorer, no shared mempool, and no way for external services to interact with your chain.
  • Custom signets are best for integration testing across independent services, multi-party protocol testing, and any scenario where you need a shared public chain with predictable timing. Mutinynet's 30-second blocks offer a middle ground between regtest's instant blocks and mainnet's 10-minute wait.
  • The default signet is best for final-stage testing before mainnet, wallet compatibility checks, and long-running test scenarios that benefit from mainnet-like timing.

A common development workflow moves through all three: iterate on regtest, validate multi-party behavior on a custom signet like Mutinynet, then perform final checks on the default signet or testnet4. Layer 2 protocols like Spark benefit from this staged approach: channel logic can be fuzzed locally on regtest, then tested against real Lightning infrastructure on Mutinynet, before final validation on the default signet.

Explorer and Tooling Availability

The practical value of a test network depends heavily on the surrounding tooling ecosystem. The default signet has the broadest support: mempool.space, Esplora, Electrum Personal Server, and most major Bitcoin node implementations all support it natively. BDK, LDK, and the Rust Bitcoin ecosystem work with the default signet out of the box.

Mutinynet provides its own parallel tooling stack: a custom mempool.space instance, an Esplora API, and a CLI tool (mutinynet-cli) that can request faucet coins, create BOLT11 invoices, pay invoices, and open channels from the command line. Wallets that support custom Esplora endpoints (such as Sparrow and many BDK-based wallets) can connect to Mutinynet by pointing their backend at mutinynet.com/api.

Bitcoin Inquisition transactions that use experimental opcodes may not appear in standard block explorers until they are confirmed in a block. Developers testing OP_CAT covenants or CTV templates should run an Inquisition node locally to see unconfirmed experimental transactions in the mempool.

Fee Environment and Realism

No signet network accurately replicates mainnet's fee market. The default signet has low transaction volume, so its mempool rarely builds meaningful backlog. Fee estimation algorithms will return minimum-relay-fee values most of the time, which is not representative of the competitive fee spikes that occur on mainnet during congestion events.

Mutinynet's 30-second blocks make fee pressure even less realistic: blocks clear the mempool 20x faster than mainnet. Applications that depend on accurate fee estimation, replace-by-fee competition, or CPFP behavior should supplement signet testing with recorded mainnet mempool data or simulation frameworks. Signet remains useful for verifying that fee-estimation code runs correctly and handles edge cases (zero-fee-rate, maximum-weight transactions), even though the fee values themselves are not representative.

Frequently Asked Questions

Can I deploy smart contracts on Bitcoin signet?

Bitcoin does not support general-purpose smart contracts like Ethereum. However, Bitcoin Inquisition activates proposed opcodes such as OP_CAT on signet, enabling developers to build and test covenant-style contracts using Bitcoin Script. sCrypt provides a TypeScript-based language that compiles to Bitcoin Script and can target signet with OP_CAT enabled. StarkWare has demonstrated STARK proof verification on signet using OP_CAT. These experiments require running the Bitcoin Inquisition client rather than standard Bitcoin Core.

Which signet has the most realistic fee environment?

None of the current signet networks replicate mainnet fee pressure accurately. The default signet comes closest because its 10-minute block interval matches mainnet, but its low transaction volume means the mempool rarely builds a meaningful backlog. For realistic fee testing, developers should replay recorded mainnet mempool data against a regtest instance or use fee simulation frameworks alongside signet integration tests.

What is the difference between Bitcoin Inquisition and a custom signet?

Bitcoin Inquisition is a modified node client, not a separate network. It runs on the default signet and enforces proposed soft fork rules that standard Bitcoin Core does not. A custom signet (like Mutinynet) is a completely separate chain with its own genesis block, challenge script, and network magic. Inquisition nodes and standard signet nodes share the same chain and can communicate, while custom signet nodes cannot connect to the default signet.

How do I connect a wallet to Mutinynet?

Any wallet that supports custom Esplora backend configuration can connect to Mutinynet. Set the Esplora API endpoint to https://mutinynet.com/api and select signet as the network. BDK-based wallets, Sparrow, and several mobile wallets support this configuration. You can then request test coins from the faucet at faucet.mutinynet.com.

Is Mutinynet still running after Mutiny Wallet shut down?

Yes. Mutiny Wallet (the Lightning wallet application) shut down on December 31, 2024, but the Mutinynet signet infrastructure continues to operate independently. The faucet, block explorer, and Lightning nodes remain available. Developer activity on the network was still observed as recently as late 2026, with new tooling being built to index its chain.

Can I run my own custom signet?

Yes. Creating a custom signet requires generating a key pair, setting the -signetchallenge flag to the hex-encoded scriptPubKey derived from your public key, and running a block signer that periodically creates signed blocks. BIP 325 also allows trivially true challenges for fully permissionless custom signets, though these lose the spam-resistance benefit of signed blocks. The Bitcoin Wiki and BIP 325 specification document the full setup process.

What happened to testnet3, and should I still use it?

Bitcoin Core deprecated testnet3 in version 28 and replaced it with testnet4. Testnet3 suffered from years of griefing attacks, unreliable block production, and testnet coins accumulating monetary value. Testnet4 addresses some of these issues but still uses proof-of-work, making it susceptible to hash-rate volatility. For most development workflows, signet offers more predictable behavior. See our testnet4 vs signet developer guide for detailed migration advice.

This tool is for informational purposes only and does not constitute financial or technical advice. Network availability, faucet limits, and infrastructure may change without notice. Always verify current network status before relying on any test environment for development.

Build with Spark

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

Read the docs →