Faucet Troubleshooting
Use this guide to diagnose rejected addresses, pending requests, explorer lookup problems, and out-of-funds messages.
Lookup a Signet Transaction or Address
Paste a Signet transaction ID or address. This browser-side helper links to the public Signet explorer and, when possible, checks the mempool.space Signet API.
Address Rejected
The faucet validates addresses against Bitcoin Signet rules. Mainnet addresses beginning with bc1, legacy mainnet addresses, regtest addresses, and malformed strings are rejected. If your wallet is set to Testnet4 or a custom signet, it may not be compatible with this default Signet faucet.
Request Still Pending
Requests are batched before broadcast. A pending request usually means it is waiting for the next batch, the faucet node is catching up, or the mempool is temporarily not accepting the transaction. Check faucet status before submitting again.
Out of Funds or Rate Limited
The faucet can run out of spendable outputs during heavy use. Rate limits protect the service from draining. Wait for the next day or try again after the next block if the public status page shows enough balance.
Explorer Disagrees With Your Wallet
Hosted explorers can lag or disagree with your local node mempool. For serious testing, confirm against your own Signet node with bitcoin-cli -signet gettransaction, getrawtransaction, or wallet balance commands.