lightningsignetfaucet.comsignet · dry

Signet sats over Lightning,
without a CAPTCHA.

Every other signet faucet asks you to prove you are human. This one asks your CPU to prove it did a second of work — which a script, a CI job, or an autonomous agent can do just as easily as you can.

Paste an invoice from any signet Lightning wallet. Your browser solves a proof-of-work challenge — about a second of CPU — and the faucet pays.

Per claim
1,000 sats
Difficulty
26 bits
Claims this hour
0
Login required
No

Or one line in a terminal

Takes a challenge, grinds it, redeems it, and waits for the payment to settle.

curl -sSL lightningsignetfaucet.com/claim.sh | sh -s -- <bolt11>

Needs python3 or node — the grind is a few million SHA-256 rounds, and a shell loop calling sha256sum manages about seventy per second. Read the script before you run it with curl -sSL lightningsignetfaucet.com/claim.sh | less.

Calling the API directly

Three calls, no key. Every response is JSON with a stable error code and a retry hint.

# 1. take a challenge
curl -s lightningsignetfaucet.com/api/challenge

# 2. find nonce where sha256(challenge + nonce)
#    has enough leading zero bits

# 3. redeem it
curl -s -X POST lightningsignetfaucet.com/api/claim \
  -H 'content-type: application/json' \
  -d '{"bolt11":"lntbs…","challenge":"…","nonce":"…"}'

The full protocol, error codes, and rules are written for agents at /llms.txt. Live status at /api/status.

Why proof of work

A faucet needs some defence against being drained. The usual answer is a CAPTCHA, which prices a claim in humanity — and locks out exactly the automated tooling that needs test sats most.

Proof of work prices a claim in energy instead. A second of CPU is nothing once; it is expensive ten thousand times. Each challenge is single-use, so the work cannot be ground once and replayed, and difficulty rises automatically with demand.