What Can You Test on Signet?
Signet is useful because it lets developers try Bitcoin behavior without mainnet risk. This directory points to experiments and networks where test sats are actually useful.
Bitcoin Inquisition Lab
Bitcoin Inquisition is a Bitcoin Core branch used to experiment with proposed consensus changes on Signet-like networks. It is interesting for OP_CAT, CTV, APO, CSFS, INTERNALKEY, and related research.
Caveat: proposals are experimental and not mainnet rules. Always label demos as non-mainnet.
Taproot Assets on Signet
Taproot Assets testing can require Signet sats for asset issuance, transfer transactions, proof handling, and Lightning-adjacent workflows. Use official Lightning Labs documentation and verify live universe endpoints before building guides around them.
Caveat: docs and service endpoints can change quickly.
Lightning on Signet
Signet is a good place to test node setup, channel workflows, invoices, fee policies, and wallet integration before touching mainnet. Public Signet liquidity is limited, so routing failures are normal and useful to handle.
Custom Signets and Mutinynet
Custom signets let teams define their own block signing rules, seed nodes, and testing cadence. Mutinynet is one example of a fast developer signet used when default Signet timing is too slow for demos.
Caveat: custom signets are separate networks. Default Signet coins and explorers will not apply.
Explorer and API Testing
Signet is handy for testing wallet indexing, mempool tracking, address histories, and transaction status UI. Public explorers are convenient for prototypes, while production-quality tools should confirm behavior against their own node or indexer.
Wallet and Address Workflows
Test signing, change outputs, fee bumping, descriptors, multisig, watch-only wallets, and address reuse warnings with test coins first. Pair this with the quickstart and wallet safety pages.