Testnet4 faucet
The SUBFROSTPOOL faucet hands out testnet4 BTC (tBTC) so you can try SUBFROST on testnet4: wrap to frBTC, swap, deploy and call alkanes contracts, use the private mempool. It is paid from the pool's own testnet4 mining. A share of every block the pool finds goes to the faucet's address through the same payout contract and frBTC unwrap that pays the miners, so the faucet refills as the pool mines.
Testnet4 coins have no value. Nothing here touches mainnet.
Request coins
You need a testnet4 address: tb1… (or a legacy m…, n…, 2…). Bitcoin Core started with -testnet4, Sparrow in testnet mode, subfrost-cli with --network signet, or the SUBFROST wallet with Settings → Network → Testnet4 will give you one. A mainnet bc1 address is refused.
Over the subtun0 overlay (no key)
The faucet is a subtun0 service with the name fr1a9scx6u2xqhfga8jct0zcq2s2ph5ctt4wrnt57jltqmqaqaerrdspnqjyn. Any of the public overlay gateways reaches it, and no API key is needed:
| Gateway | Base URL |
|---|---|
| subdns.to | https://fr1a9scx6u2xqhfga8jct0zcq2s2ph5ctt4wrnt57jltqmqaqaerrdspnqjyn.subdns.to |
| asilos.ltd | https://fr1a9scx6u2xqhfga8jct0zcq2s2ph5ctt4wrnt57jltqmqaqaerrdspnqjyn.asilos.ltd |
| fr.style | https://fr1a9scx6u2xqhfga8jct0zcq2s2ph5ctt4wrnt57jltqmqaqaerrdspnqjyn.fr.style |
FAUCET=https://fr1a9scx6u2xqhfga8jct0zcq2s2ph5ctt4wrnt57jltqmqaqaerrdspnqjyn.subdns.to
curl -s -X POST "$FAUCET/v1/faucet" \
-H 'content-type: application/json' \
-d '{"address": "tb1q…your testnet4 address…"}'
A subtun0 client (the native client or the wasm one in a browser) can also dial fr1a9scx…qjyn.peer on port 80 directly.
Over HTTPS on testnet4.subfrost.io (SUBFROST API key)
The same API is at https://testnet4.subfrost.io/v1/faucet. This path needs a SUBFROST API key, the same key you use for testnet4.subfrost.io/v4/<key>, sent in the x-subfrost-api-key header. Requests on this path are counted per key.
curl -s -X POST https://testnet4.subfrost.io/v1/faucet \
-H "x-subfrost-api-key: $SUBFROST_API_KEY" \
-H 'content-type: application/json' \
-d '{"address": "tb1q…your testnet4 address…"}'
The answer
A granted request answers 202 and is queued:
{
"id": 42,
"status": "queued",
"address": "tb1q…",
"amount_sats": 5000000,
"amount_btc": "0.05000000",
"payout_number": 1,
"message": "queued: it goes out in the faucet's batch transaction at the next testnet4 block",
"status_url": "/v1/faucet/requests/42",
"next_eligible_at": 1792260000
}
The faucet pays everyone queued in one transaction per testnet4 block. When the next block arrives it broadcasts that transaction, and the request's status moves from queued to sent (with the txid) and then to confirmed:
curl -s "$FAUCET/v1/faucet/requests/42"
{"id": 42, "status": "sent", "amount_sats": 5000000, "txid": "…", "vout": 0, "url": "https://mempool.space/testnet4/tx/…"}
Testnet4 confirmations can be slow: many public testnet4 blocks are empty difficulty-1 blocks, so a transaction waits for a full block or one mined by SUBFROSTPOOL. The faucet's transactions pay 2 sat/vB, above what testnet4 needs today.
Other answers:
| Status | Meaning |
|---|---|
400 | Not a testnet4 address, or not {"address": "…"}. message says which. |
429 | Too soon for this address or caller. next_eligible_at (unix seconds) and the Retry-After header say when to come back. |
503 | The faucet is empty or today's budget is spent. It refills as the pool mines. |
Check before you ask
GET /v1/faucet/info shows the faucet's balance, the current amounts, recent batch transactions, and under you whether you can ask now and how much you would get. Add ?address=tb1… to check a specific address.
curl -s "$FAUCET/v1/faucet/info?address=tb1q…" | jq '.first_payout_sats, .you'
How much you get
Your first request gets 0.05 tBTC (5,000,000 sats) while the faucet holds 5 tBTC or more. At today's testnet4 fee rates of about 1 sat/vB, an alkanes call or a swap costs a few hundred sats in fees, so 0.05 tBTC covers thousands of transactions with plenty left to wrap into frBTC and trade.
Later requests get less. The total you can collect grows with the logarithm of the number of requests, so asking again helps a little and asking many times helps very little:
| Request | Amount | Total so far | Wait before the next one |
|---|---|---|---|
| 1st | 0.05 | 0.05 | 1 hour |
| 2nd | 0.0347 | 0.0847 | 2 hours |
| 3rd | 0.0203 | 0.1049 | 4 hours |
| 4th | 0.0144 | 0.1193 | 8 hours |
| 5th | 0.0112 | 0.1305 | 16 hours |
| 10th | 0.0053 | 0.1651 |
(amounts in tBTC)
The precise rule: request number k is paid B·ln(k/(k−1)), the first is B, so k requests add up to B·(1 + ln k). B is 0.05 tBTC, or one hundredth of the faucet's balance if that is smaller, so a nearly empty faucet hands out smaller amounts to more people instead of a few large ones.
Limits
- 10 payouts per 30 days per caller, with the wait doubling after each one (1 h, 2 h, 4 h, … up to 7 days).
- Who counts as the same caller. Every request counts against the destination address, and against the API key on the HTTPS path or the client IP (its /24, or /48 for IPv6) on the overlay path. The strictest of these decides. A new address does not reset a key, and a new key does not reset an address.
- Daily budget. At most a quarter of the faucet's coins go out in any 24 hours. When that is spent the faucet answers
503until older payouts age out or the pool mines more. - Busy periods. Each path pays at most 60 requests an hour in total, and each caller may make 6 requests a minute.
- Payouts under 0.001 tBTC are not made.
What it is for
Testing on testnet4: wrapping BTC to frBTC and back, swaps on the testnet4 AMM pools, deploying and calling alkanes contracts, the private mempool, and pointing apps at testnet4.subfrost.io/v4/<key>. If you need more than the faucet gives, mine on the testnet4 stratum: miners are paid in tBTC for every block the pool finds.
Please send what you no longer need back to the faucet. Its address is faucet_address in /v1/faucet/info.