Get Lightning Signet test sats

Use a wallet that supports Bitcoin Signet

Select the Bitcoin Signet network in a wallet or Lightning node that explicitly supports it. A mainnet Lightning wallet or a testnet-only configuration is not compatible. Your receiver must be online and able to accept a routed payment on the same Signet network.

If you operate your own Lightning node, check its network configuration and receiving capacity before creating an invoice. ArkFaucet supplies a test payment; it does not configure channels or provide a Lightning wallet.

For agent automation, use the OpenClaw setup or Hermes Agent setup and supply the invoice as the destination.

1. Create and check an invoice

1. Choose Receive in your Signet wallet and create a fresh BOLT11 invoice for 500, 1,000, or 1,500 sats.
2. Copy the entire invoice. It must begin lntbs; do not shorten it, modify the prefix, or omit characters.
3. Confirm that it is unexpired and its amount matches the faucet amount you will select. An amountless invoice also works with a supported faucet amount.

A BOLT11 invoice is a payment request, not a reusable Lightning address. An email-style address or BOLT12 offer cannot be used in this field.

Recognize the network prefix

The prefix is an initial check, not proof that an invoice is otherwise valid or payable. The faucet also validates its network, amount, and invoice data.

2. Request sats in the browser

1. Open the faucet form.
2. Select Lightning as the payment rail.
3. Paste the full fresh lntbs invoice and select the matching amount.
4. Request Signet sats once and read the result.

No account, API key, or CAPTCHA is required. Signet coins have no monetary value.

Or use the Lightning faucet API

Check availability first:

curl --fail --silent --show-error https://arkfaucet.com/api/status

Replace the placeholder below with the complete fresh invoice from your wallet. This example requests 500 sats, so use a 500-sat or amountless invoice.

curl --silent --show-error --include https://arkfaucet.com/api/request \
  -H 'Content-Type: application/json' \
  --data '{"rail":"lightning","destination":"lntbsYOUR_COMPLETE_INVOICE","amount_sats":500}'

A successful response is HTTP 200. This is an example of its required fields, not a live payment receipt:

{"success":true,"status":"sent","amount_sats":500,"network":"signet","rail":"lightning","transport":"clearnet"}

3. Confirm receipt

Check the invoice status and received balance in your wallet. Preserve the distinction between a request being submitted and the receiver showing it as paid. Public faucet activity charts contain aggregate totals; they cannot prove that a specific invoice settled.

Receiving sats from this faucet uses an invoice generated by your wallet. The separate “Fund this faucet” form generates an invoice payable to ArkFaucet for contributions.

Common Lightning problems

• Wrong network: create a new invoice in a Signet wallet. Never edit a mainnet or testnet invoice to look like Signet.
• Amount mismatch: select the amount encoded in your invoice. If it is not supported, create an invoice for a supported amount before making a claim.
• Expired invoice: create a fresh one. If a previous payout is uncertain, resolve that status before requesting another payment.
• Payment cannot route: check that the receiver is online and has usable receiving capacity on the correct Signet network. The Lightning payment lifecycle explains the routing requirement.
• Rate limit: stop on HTTP 429 and report the retry time. Changing invoices does not bypass shared limits.
• Uncertain payment: stop on payout_unknown; do not submit a replacement.

Read current limits before automating. Clearnet claims share an IP limit of five per rolling 24 hours, a destination limit, and a balance-scaled global allowance. See the agent guide for other error responses and transport limits.

Keep building

Read the faucet skill, OpenAPI contract, or compact service documentation. Privacy transport setup: Tor and I2P.