You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix key naming, alt text, stale references, incorrect signers, and update mint-005 reference transactions
- mint-005: Update reference transactions and example timestamps to match
current signet vault (smallest=1753488000, between=1766880000, largest=1770768000)
- mint-005: Fix Layer 2 Example Spend signers (verified against on-chain witness data)
- mint-005: Add Layer 3 Example Spend signer list
- mint-006: Fix stale "10-Key Collaborative Custody Vault" references, add note
clarifying layer reordering and PK/PAK column swap vs MINT-005
- mint-006/007/008: Fix image alt text from CK to PAK
- mint-009: Fix CK/CSK to PAK/SAK in descriptor, policy, and example spend
Copy file name to clipboardExpand all lines: mint-005.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -202,7 +202,7 @@ Layer is used as an abstraction to segment the different eligible spending condi
202
202
203
203
---
204
204
# Example Miniscript Output Descriptor
205
-
For this example, the `smallest_epoch_timestamp` is: 1672531200 (Jan 1 2023, midnight gmt), the `between_epoch_timestamp` is: 1673740800 and `largest_epoch_timestamp` is: 1675209600 (Feb 1 2023, midnight gmt)
205
+
For this example, the `smallest_epoch_timestamp` is: 1753488000 (July 26, 2025 00:00:00 UTC), the `between_epoch_timestamp` is: 1766880000 (December 28, 2025 00:00:00 UTC) and `largest_epoch_timestamp` is: 1770768000 (February 11, 2026 00:00:00 UTC)
Copy file name to clipboardExpand all lines: mint-006.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,8 @@
6
6
7
7
This vault is very similar to [mint-005.md](mint-005.md). The difference is the sequential order of the 3rd and 4th "layers", where the Principal is able to unilaterally move funds prior to the recovery layer. This is done for users who wish to make sure that funds will require the Principal to sign before the Primary Agent and Secondary Agent are able to move funds unilaterally. The recovery layer still exists to provide support to recover funds in the event the Principal has lost access to their keys.
8
8
9
+
**Key differences from MINT-005:** First, the layer ordering is changed — the Sovereign Recovery Path (Recovery Keys only) comes *before* the Emergency Recovery Path (Primary Agent + Secondary Agent), meaning the Principal can unilaterally move funds before the agents gain the ability to recover without the Principal. Second, the Primary Agent Keys (PAKs) are listed as Key Set 1 and the Principal Keys (PKs) as Key Set 2 in the summary table and layer diagrams, which is the reverse of MINT-005's column ordering. Together, these changes result in a different miniscript output descriptor.
10
+
9
11
10
12
### More on Timelock Values
11
13
@@ -19,7 +21,7 @@ There are three timelocks used for this MinT:
19
21
20
22
### Keys
21
23
22
-
In total, there are 10 keys in use for the 10-Key Collaborative Custody Vault, they are as follows:
24
+
In total, there are 10 keys in use for the 3 Key Joint Custody, Sovereign First Vault, they are as follows:
@@ -30,11 +32,11 @@ In total, there are 10 keys in use for the 10-Key Collaborative Custody Vault, t
30
32
31
33
32
34
33
-
Below are reference diagrams on how the 10-Key Collaborative Custody Vault operates across time:
35
+
Below are reference diagrams on how the 3 Key Joint Custody, Sovereign First Vault operates across time:
34
36
35
37
---
36
38
37
-
### Collaborative Custody Summary Layers
39
+
### Joint Custody Summary Layers
38
40
39
41
Layer is used as an abstraction to segment the different eligible spending conditions, going in an ascending order of timelock values. At the start, only "Layer 1" is accessible for spending funds, over time, other spending conditions become available, but this does not restrict the ability to spend from a preceding layer.
40
42
@@ -63,9 +65,9 @@ Layer is used as an abstraction to segment the different eligible spending condi
63
65
</tr>
64
66
<tr>
65
67
<td align="center">2 of 3 PAKs AND 2 of 3 PKs</td>
0 commit comments