From 8255929de4087fa2ef7a3bf360f2d377017c7b09 Mon Sep 17 00:00:00 2001
From: callebtc <93376500+callebtc@users.noreply.github.com>
Date: Fri, 15 Nov 2024 16:34:58 +0100
Subject: [PATCH] add missing NUT-06 settings (#191)

---
 07.md | 12 ++++++++++++
 08.md | 12 ++++++++++++
 09.md | 12 ++++++++++++
 10.md | 12 ++++++++++++
 11.md | 12 ++++++++++++
 12.md | 12 ++++++++++++
 14.md | 12 ++++++++++++
 15.md |  2 +-
 17.md |  2 +-
 9 files changed, 86 insertions(+), 2 deletions(-)

diff --git a/07.md b/07.md
index c4caf4e..4589120 100644
--- a/07.md
+++ b/07.md
@@ -99,6 +99,18 @@ curl -X POST https://mint.host:3338/v1/checkstate -H 'Content-Type: application/
 
 Where `Y` belongs to the provided `Proof` to check in the request, `state` indicates its state, and `witness` is the witness data that was potentially provided in a previous spend operation (can be empty).
 
+## Mint info setting
+
+The [NUT-06][06] `MintMethodSetting` indicates support for this feature:
+
+```json
+{
+  "7": {
+    "supported": true
+  }
+}
+```
+
 [00]: 00.md
 [01]: 01.md
 [02]: 02.md
diff --git a/08.md b/08.md
index db62531..d03ffcd 100644
--- a/08.md
+++ b/08.md
@@ -132,6 +132,18 @@ If the mint has made a successful payment, it will respond the following.
 
 The field `change` is an array of `BlindSignatures` that account for the overpaid fees. Notice that the amount has been changed by the mint. `Alice` must take these and generate `Proofs` by unblinding them as described in [NUT-00][00] and as she does in [NUT-04][04] when minting new tokens. After generating the `Proofs`, `Alice` stores them in her database.
 
+## Mint info setting
+
+The [NUT-06][06] `MintMethodSetting` indicates support for this feature:
+
+```json
+{
+  "8": {
+    "supported": true
+  }
+}
+```
+
 [00]: 00.md
 [01]: 01.md
 [02]: 02.md
diff --git a/09.md b/09.md
index e4b3b32..73eee23 100644
--- a/09.md
+++ b/09.md
@@ -37,6 +37,18 @@ The mint `Bob` then responds with a `PostRestoreResponse`.
 
 The returned arrays `outputs` and `signatures` are of the same length and for every entry `outputs[i]`, there is a corresponding entry `signatures[i]`.
 
+## Mint info setting
+
+The [NUT-06][06] `MintMethodSetting` indicates support for this feature:
+
+```json
+{
+  "9": {
+    "supported": true
+  }
+}
+```
+
 [00]: 00.md
 [02]: 02.md
 [03]: 03.md
diff --git a/10.md b/10.md
index 70f52e6..c909464 100644
--- a/10.md
+++ b/10.md
@@ -56,6 +56,18 @@ Example use cases of this secret format are
 - [NUT-11][11]: Pay-to-Public-Key (P2PK)
 - [NUT-14][14]: Hashed Timelock Contracts (HTLCs)
 
+## Mint info setting
+
+The [NUT-06][06] `MintMethodSetting` indicates support for this feature:
+
+```json
+{
+  "10": {
+    "supported": true
+  }
+}
+```
+
 [00]: 00.md
 [01]: 01.md
 [02]: 02.md
diff --git a/11.md b/11.md
index b84619f..130f0f8 100644
--- a/11.md
+++ b/11.md
@@ -172,6 +172,18 @@ The following use cases are unlocked using P2PK:
 - Ecash that is owned by multiple people via the multisignature abilities
 - Atomic swaps when used in combination with the locktime feature
 
+## Mint info setting
+
+The [NUT-06][06] `MintMethodSetting` indicates support for this feature:
+
+```json
+{
+  "11": {
+    "supported": true
+  }
+}
+```
+
 [00]: 00.md
 [01]: 01.md
 [02]: 02.md
diff --git a/12.md b/12.md
index a78308b..1b23d42 100644
--- a/12.md
+++ b/12.md
@@ -130,6 +130,18 @@ R1 = ... (same as Alice)
 
 If a DLEQ proof is included in a received token, wallets **MUST** verify the proof.
 
+## Mint info setting
+
+The [NUT-06][06] `MintMethodSetting` indicates support for this feature:
+
+```json
+{
+  "12": {
+    "supported": true
+  }
+}
+```
+
 [00]: 00.md
 [01]: 01.md
 [02]: 02.md
diff --git a/14.md b/14.md
index 8dbeac6..9b76f0d 100644
--- a/14.md
+++ b/14.md
@@ -60,6 +60,18 @@ See [NUT-11][11] for a description of the signature scheme, the additional use o
 
 The witness for a spent proof can be obtained with a `Proof` state check (see [NUT-07][07]).
 
+## Mint info setting
+
+The [NUT-06][06] `MintMethodSetting` indicates support for this feature:
+
+```json
+{
+  "14": {
+    "supported": true
+  }
+}
+```
+
 [00]: 00.md
 [01]: 01.md
 [02]: 02.md
diff --git a/15.md b/15.md
index ac4a65b..52efe74 100644
--- a/15.md
+++ b/15.md
@@ -38,7 +38,7 @@ The wallet `Alice` includes the following `PostMeltQuoteBolt11Request` data in i
 
 Here, `request` is the bolt11 Lightning invoice to be paid, `unit` is the unit the wallet would like to pay with, and `amount` is the amount for the requested payment. The wallet then pays the returned melt quote the same way as in [NUT-05][05].
 
-## Settings
+## Mint info setting
 
 The settings returned in the info endpoint ([NUT-06][06]) indicate that a mint supports this NUT. The mint MUST indicate each `method` and `unit` that supports `mpp`. It can indicate this in an array of objects for multiple `method` and `unit` pairs and the boolean flag `mpp` set to `true`.
 
diff --git a/17.md b/17.md
index 127d815..5603237 100644
--- a/17.md
+++ b/17.md
@@ -228,7 +228,7 @@ Wallet:
 }
 ```
 
-## Signaling Support via NUT-06
+## Mint info setting
 
 Mints signal websocket support via [NUT-06][06] using the following setting: