From d6297ebccb9fb867446a19b60e86910410dffcc5 Mon Sep 17 00:00:00 2001 From: callebtc <93376500+callebtc@users.noreply.github.com> Date: Sat, 14 Jan 2023 22:15:58 +0100 Subject: [PATCH] format --- docs/specs/00.md | 2 +- docs/specs/01.md | 2 +- docs/specs/02.md | 2 +- docs/specs/03.md | 2 +- docs/specs/04.md | 2 +- docs/specs/05.md | 2 +- docs/specs/06.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/specs/00.md b/docs/specs/00.md index f5733dd..250e7ae 100644 --- a/docs/specs/00.md +++ b/docs/specs/00.md @@ -1,4 +1,4 @@ -# NUT-0 - Notation and Models +# NUT-0: Notation and Models Sending user: `Alice` Receiving user: `Carol` diff --git a/docs/specs/01.md b/docs/specs/01.md index 8275fbb..7d83ee2 100644 --- a/docs/specs/01.md +++ b/docs/specs/01.md @@ -1,4 +1,4 @@ -# NUT-1 - Mint public key exchange +# NUT-1: Mint public key exchange This describes the basic exchange of the public mint keys that the wallet user `Alice` uses to unblind `Bob`'s signature. diff --git a/docs/specs/02.md b/docs/specs/02.md index 049552d..0a05ec4 100644 --- a/docs/specs/02.md +++ b/docs/specs/02.md @@ -1,4 +1,4 @@ -# NUT-2 - Keysets and keyset ID +# NUT-2: Keysets and keyset ID A keyset is a set of public keys that the mint `Bob` generates and shares with its users. It refers to the set of public keys that each correspond to the amount values that the mint supports (e.g. 1, 2, 4, 8, ...) respectively. diff --git a/docs/specs/03.md b/docs/specs/03.md index 81cc7fa..7296d46 100644 --- a/docs/specs/03.md +++ b/docs/specs/03.md @@ -1,4 +1,4 @@ -# NUT-3 - Request mint +# NUT-3: Request mint Minting tokens is a two-step process: requesting a mint and minting the tokens. Here, we describe the first step. A wallet requests the minting of tokens in exchange for paying a bolt11 Lightning invoice (typically generated by the mint to add funds to its reserves, and typically paid with another Lightning wallet). diff --git a/docs/specs/04.md b/docs/specs/04.md index 7747ba0..b2f0fd1 100644 --- a/docs/specs/04.md +++ b/docs/specs/04.md @@ -1,4 +1,4 @@ -# NUT-4 - Mint tokens +# NUT-4: Mint tokens After requesting a mint (see #3 [TODO: Link]) and paying the invoice that was returned by the mint, a wallet proceeds with requesting tokens from the mint in return for paying the invoice. diff --git a/docs/specs/05.md b/docs/specs/05.md index 2034dd8..10378fe 100644 --- a/docs/specs/05.md +++ b/docs/specs/05.md @@ -1,4 +1,4 @@ -# NUT-5 - Melting tokens +# NUT-5: Melting tokens Melting tokens is the opposite of minting them (see #4): the wallet `Alice` sends `Proofs` to the mint `Bob` together with a bolt11 Lightning invoice that `Alice` wants to be paid. To melt tokens, `Alice` sends a `POST /melt` request with a JSON body to the mint. The `Proofs` included in the request will be burned by the mint and the mint will pay the invoice in exchange. diff --git a/docs/specs/06.md b/docs/specs/06.md index 8910469..9f5e136 100644 --- a/docs/specs/06.md +++ b/docs/specs/06.md @@ -1,4 +1,4 @@ -# NUT-6 - Split tokens +# NUT-6: Split tokens The split operation is the most important component of the Cashu system. The wallet `Alice` can use it to redeem tokens (i.e. receive new ones in return) that she received from `Carol`, or she can split her own tokens to a target amount she needs to send to `Carol`, if she does not have the necessary amounts to compose the target amount in her wallet already.