Regtest
A private network where blocks are mined on demand, so confirmations are instant. Best for fast iteration, automated tests, and demos. State on regtest is the most ephemeral and may be reset from time to time.
Supported Networks
Sigvault runs a separate, isolated deployment for each Bitcoin network it supports. Wallets, devices, and signing ceremonies created on one network never appear on another. Pick the network that matches what you are doing today; you can move to another at any time without affecting the first.
At a glance
Section titled “At a glance”| Network | Status | Real value? | Dashboard | API | Address prefix |
|---|---|---|---|---|---|
| Regtest | Live | No | regtest.sigvault.org | api.regtest.sigvault.org | bcrt1… |
| Signet | Live | No | signet.sigvault.org | api.signet.sigvault.org | tb1… |
| Testnet | Live | No | testnet.sigvault.org | api.testnet.sigvault.org | tb1… / m… |
| Mainnet | Coming soon | Yes | — | — | bc1… / 1… |
None of the live networks carry real bitcoin. Coins on regtest, signet, and testnet are free and worthless — use them freely to learn, build, and break things.
How they differ
Section titled “How they differ”Signet
A public, federated test network. Blocks come at a steady ~10-minute cadence, the chain is stable, and faucets are reliable. Best for realistic end-to-end testing — multisig ceremonies, time-locked vaults, mempool behavior — without the noise and sluggishness of testnet.
Testnet
The original public test network. Larger and noisier than signet, with unpredictable block times and frequent reorgs. Useful for interop testing against tools that only speak testnet. Most new projects should prefer signet.
Mainnet
Real Bitcoin. Real consequences. Sigvault mainnet is in active preparation and not yet open. Do not move funds you cannot afford to lose when it launches; treat early access as beta software.
Choosing a network
Section titled “Choosing a network”| If you want to… | Use |
|---|---|
| Click around the UI without waiting for blocks | Regtest |
| Test a multisig flow end-to-end with realistic timing | Signet |
| Reproduce a bug against an existing testnet tool | Testnet |
| Custody real bitcoin | Mainnet (when available) |
If in doubt: start on signet. It behaves like mainnet without the cost.
Getting test coins
Section titled “Getting test coins”Sigvault does not run faucets. Use these public ones:
- Signet — signetfaucet.com, signet.bublina.eu.org
- Testnet — bitcoinfaucet.uo1.net, coinfaucet.eu/en/btc-testnet
- Regtest — coins are issued on request from the dashboard.
Switching networks
Section titled “Switching networks”Web dashboard
Section titled “Web dashboard”The landing page at sigvault.org lists every live deployment. Pick one and you are sent to that network’s dashboard. Each dashboard requires a separate sign-in — accounts are not shared across networks.
Desktop application
Section titled “Desktop application”The desktop signer is a single application that supports every network. On first launch it asks which network to connect to; the choice is remembered until you sign out. To switch, sign out and use the Change button on the login screen. New networks appear in the picker automatically as they go live.
Hardware wallet behavior across networks
Section titled “Hardware wallet behavior across networks”Bitcoin descriptors and PSBTs are network-specific — a signature for a testnet address is not a signature for the mainnet address with the same derivation path. Most hardware wallets enforce this: if your device is in mainnet mode and you ask it to sign a regtest transaction, it will refuse.
When using Sigvault on a non-mainnet network:
- Trezor — automatically detects the network from the descriptor.
- Ledger — open the Bitcoin Test app for any non-mainnet network; the standard Bitcoin app will reject testnet-prefix descriptors.
- BitBox02 — non-mainnet support is enabled in firmware; the device prompts confirm the network on screen.
- Coldcard — set the device-level network mode to match (Settings → Danger Zone → Testnet Mode).
- Jade — switches automatically based on the descriptor.
If a sign request fails immediately with a network-mismatch error, your device is configured for a different network than the wallet you are signing for.
Next steps
Section titled “Next steps”- Set up the Desktop Application to connect a hardware wallet on any network
- Create your first Multisig Wallet on signet
- Read about User Managed Keys to understand what crosses the network boundary