Specifications about #nut
Page 2 of 2

NUT-00: Notation, Utilization, and Terminology
The notation, models and cryptography the rest of the specification is written in: blinding, signing, proofs, and how a token is serialised.
mandatory#cashu#ecash#nut
NUT-21: Clear Authentication
How a mint restricts its endpoints to users holding a token from an OpenID Connect service it trusts.
optional#cashu#ecash#nut
NUT-02: Keysets and fees
Keysets: how an id is derived from one, how a mint rotates them, and the input fee a wallet pays when spending ecash from one.
mandatory#cashu#ecash#nut
NUT-01: Mint public key exchange
How a wallet fetches a mint's active public keys, one per amount, and what a keyset is.
mandatory#cashu#ecash#nut
NUT-10: Spending conditions
The well-known secret format that turns a proof's secret into a spending condition the mint enforces.
optional#cashu#ecash#nut
NUT-15: Partial multi-path payments
Paying one Lightning invoice from several mints at once, all of them or none.
optional#cashu#ecash#nut
NUT-19: Cached Responses
Response caching on the critical endpoints, so a wallet can safely replay a request that a network error interrupted.
optional#cashu#ecash#nut
NUT-09: Restore signatures
How a wallet asks the mint to reissue blind signatures it once received, so a lost wallet can be restored.
optional#cashu#ecash#nut
NUT-07: Token state check
How a wallet asks the mint whether a proof is unspent, pending, or already spent.
optional#cashu#ecash#nut
NUT-16: Animated QR codes
How to show a token too large for a static QR code as an animated one, using the UR protocol.
optional#cashu#ecash#nut
NUT-03: Swap tokens
The swap operation, where a wallet hands proofs to the mint and receives new blind signatures in return.
mandatory#cashu#ecash#nut