Specifications about #ecash

The info endpoint, where a mint declares its name, its keys, its contacts, and which NUTs it supports.

Secrets derived from a seed phrase, so a wallet can regenerate its ecash after losing the device that held it.

Minting several quotes in one atomic request.

Melting: the two-step flow where a wallet asks the mint to pay a request and spends ecash to cover it.

Minting: the two-step flow where a wallet requests a quote, pays it, and then asks the mint to issue ecash.

A bech32m encoding of payment requests, smaller than the CBOR form and friendlier to QR codes.

A request format carrying everything a sending wallet needs, so a transaction can be started by whoever is being paid.

Binding a mint quote to a public key, so only the holder of the matching secret key can redeem it.

Minting and melting with onchain Bitcoin payments.

Minting and melting with bolt12 Lightning offers.

Minting and melting with bolt11 Lightning invoices, the method specifics on top of the shared mint and melt flows.

How a wallet backs up its mint list to Nostr relays, encrypted under keys derived from its own seed phrase.

Ecash locked to the hash of a preimage and a deadline, which makes atomic swaps between users possible.

Blinding the receiver's public key on each payment, so the mint cannot link several of them to the same person.

How an HTTP server demands payment with a 402 response carrying a Cashu payment request.

DLEQ proofs, which let anyone verify a mint's signature offline with nothing but its public keys.

Locking ecash to a public key, redeemable only against a Schnorr signature from the key that owns it.

A JSON-RPC WebSocket protocol for subscribing to quote and proof state changes instead of polling for them.

Blank outputs, which let a mint return the Lightning fees a wallet overpaid when melting.

Blind authentication tokens, which let a mint restrict access to registered users without learning which one is calling.