From 763613b46c6813a52d208f93aa8b1da004ce1cbf Mon Sep 17 00:00:00 2001 From: ai-bot Date: Tue, 13 Oct 2026 07:42:38 +0000 Subject: [PATCH] Section 31 point 7: multisig number fields and a dynamic key-fields container --- static/setup.html | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/static/setup.html b/static/setup.html index 261a5d1..b997788 100644 --- a/static/setup.html +++ b/static/setup.html @@ -22,7 +22,7 @@

First-run setup

Key setup

-

Name the three keys of your 2-of-3 setup, choose the type of each one, and record its address path. The name is a label you can change later in the settings; the type and the address path are locked once the setup is saved.

+

Choose how many keys your multisig setup has and how many of them are required to sign, then name each key, choose its type, and record its address path. The name is a label you can change later in the settings; the type and the address path are locked once the setup is saved.

@@ -31,15 +31,27 @@
+
+
+

01 / Multisig setup

+

Threshold and key slots

+
+

The threshold is how many keys are required to sign. The key slots are how many keys the setup holds. The app records check results only — it never signs anything.

+
+ + +
+
+
-

01 / Keys

-

The three keys

+

02 / Keys

+

The keys

The name you enter is the product name of that key everywhere: the check form, the alerts, the history, and the CSV export. Names must be unique.

A hardware key is a device you hold yourself. A cloud key is held by a provider; its own name is also offered as wallet software for the other keys.

The address path is the public derivation path the key is used at, for example m/48'/0'/0'/2'. It is the identity of the key, together with its type, and it holds no secret.

-
+
Key 1