LUD-25 turns an ordinary LNURL-withdraw k1 into a bearer note. Each note
is a taproot output key, opened by any spend Bitcoin's own script rules accept: a
hashlock, a signature, a timelock or a multi-party leaf. Copy it, print it, tap it
over NFC, hand it to whoever's next to you. There's no new endpoint. A wallet that
has never heard of LNURLcash sees a plain
LUD-03
withdraw link and cashes it out.
A plain withdraw link pays whoever holds the string. LUD-25 keeps the link as it is, but
the k1 becomes a spend of a taproot output key Q. The mint only
tracks Q → value, and Bitcoin script decides what holding the note means.
01
Zero new endpoints
A note is still a withdrawRequestk1, and any LUD-03 wallet can melt it to a BOLT-11 invoice. Minting only needs a wallet that can attach a LUD-12 comment.
02
Any script condition
A key-path signature (ck1), a script-path spend (cw1), or a plain bearer preimage as 64 hex characters. One rule covers all of them, checked by Bitcoin Core's own interpreter, libbitcoinkernel.
03
Bound to one mint
Signatures are made over a fixed, never-broadcast spend transaction tied to the mint's domain, so a signature made for one mint can't be replayed at another.
04
Offline circulation
A cs1 certificate, signed by the mint's node key, travels with the note. A recipient can check it with no signal, then rotate the note once they're back online.
Timelocks are checked against the mint's clock. That makes them a custodial policy, not a consensus guarantee.
ONE CALLBACK, FIVE OPERATIONS
Mint it, move it, melt it.
Your wallet generates every new note itself and shows the mint only its public
cp1. The mint never sees a secret it could spend. If any spend in a request
fails, nothing is burned or minted.
OperationRequestResult
MintpayRequest · comment=cp1<Q>Pay the invoice and Q is credited with the amount, less any advertised mint fee.
Meltcallback?k1=…&pr=lnbc…The invoice is paid, and the note burns once the payment settles. This is plain LUD-03.
Rotatecallback?k1=…&p1=cp1…The note is burned and the same value is minted at p1. Do this as soon as you receive a note.
Splitcallback?k1=…&amount=…&p1=…&p2=…p1 gets amount and p2 gets the change.
Mergecallback?k1=…&k1=…&p1=…All the notes are burned, and one note worth their sum is minted at p1.
To check a note without revealing its spend, send ?p=cp1… to the informational GET.
LUD·26 — DETERMINISTIC NOTES
Twelve words bring every note back.
LUD-26 derives key-path notes from a seed, with one hardened branch per mint, so a wallet
can lose its storage and still recover its notes.
01
One branch per mint
Derived under m/139' with LUD-05's domain hashing, and split into wallet, change and Lightning Address counters, the way an HD wallet keeps receive and change apart.
02
Recovery by scan
Re-derive each key and ask the mint with ?p= until you reach a gap limit. Each signature is deterministic, so recovered notes can be spent right away.
03
Watch-only cx1
An xpub for notes. A bookkeeping tool or a point-of-sale terminal can list every note on a branch without being able to spend any of them.
04
A Lightning Address that mints
Register a cx1 at a mint, and each payment to you@mint lands as a note on your seed. Payers at the same mint can send by internal transfer, with no Lightning payment.
THE LNURLCASH STACK
Issued. Carried. Secured.
Open-source implementations of LUD-25 and LUD-26. You can run any of them, and every
note also works in any LNURL-withdraw wallet that has never heard of LNURLcash.
01 · ISSUED
Mint
Pay a Lightning Address. Get a banknote.
A backend that issues notes on plain LUD-03 withdrawRequest and LUD-06
payRequest. Your wallet pays the mint's Lightning Address with the note's
cp1 as comment, and the mint credits it. Every spend is checked by
Bitcoin Core's interpreter.
Rotate, split, merge, or melt any note back to sats
cs1 certificates, LUD-21 verify, mint fees
Lightning Address auto-mint for registered cx1s
Python (lnd, cln, spark), Rust with its own ldk-node, or a CLN plugin
A single static page that keeps notes encrypted under your seed phrase in local
storage, and talks directly to the mint that issued each note. It works with any
mint that follows the spec. There is also a native desktop wallet.
Scan, paste, or NFC-tap a note, then verify it and rotate it at once
Generates every new secret itself and pins each mint's key
An ESP32-S3 hardware wallet built for LNURLcash. Note secrets come from a hardware
RNG, and the device reveals only their hash until the mint confirms. A secret leaves
the device only when you press a button.
Hold both buttons to show a note as an on-screen QR code
Works fully offline. No pairing is needed to browse notes
A hosted lnurl-mint-rust,
unmodified, with its own Lightning node. LSPS2 opens inbound channels just in time,
and a shared full node keeps it synced. Sign in with nostr, name your mint, and it goes
live at you.run.lnurlcash.com. It's the same open-source mint, so you
can take its data directory and run it yourself.