The multi-signature vault

When your brand mints or burns tokens, the operation is proposed to the brand's Safe vault and must gather a fixed number of signatures. This tab shows the vault configuration and the transaction list. It is where you add your signature, then broadcast on chain a transaction that has reached its threshold.

#What the screen shows

• A "Multi-sig" header with the subtitle "Safe multi-signature wallet for your brand".
• A "Safe Configuration" section: the vault address, truncated and copyable, the Chain ID, the threshold as "threshold out of owner count", and the status.
• Three contract role badges, Minter, Burner and Admin, then an "Owner Wallets" table giving the address and the label of your brand's wallets. The SealTrust signing wallet is not listed there, although it counts in the owner number shown next to the threshold.
• A "Transactions" section with a counter, a Pending or All filter, and a Refresh button. The Pending filter hides transactions already executed.
• A table of six columns: Type, Status, Confirmations, Proposed, Safe TX Hash, Actions. The signature counter is shown as "signatures gathered out of threshold" and turns green as soon as the threshold is reached.
• An expandable row showing the transaction payload, when there is one.
• A "How it works" section in three steps.
• A brand selector, when the account is attached to several brands.

#What you can do here

• Add your signature with "Approve". A browser confirmation opens first, naming the operation type.
• Re-sync the signatures with "Sync", broadcast with "Execute" a transaction that has reached its threshold.
• Switch between pending transactions and all transactions, and refresh by hand, on top of the automatic refresh every 30 seconds.
• Copy the vault address, a wallet address, or a transaction hash.

#What controls access

• The "Multisig" tab is hidden for the basic and DPP profiles. The page stays reachable by its address: the only condition set is an authenticated administrator session.
• The buttons depend on the transaction state. "Approve" only appears on a transaction awaiting signatures, "Execute" only on a transaction ready to broadcast, and "Sync" disappears on a transaction already executed.
• Broadcasting demands two things: retyping the exact phrase served by the server, and supplying a fresh two-factor code. The server only computes that phrase for an opened transaction, and the screen never rebuilds it. It ties the operation to its target, for example "{op} token {token_id}" or "{op} chip {uid_hash}".
• The second factor is required independently of the brand: the vault threshold can never waive it.
• When your signature brings the threshold up, a message invites you to click Execute and announces those two demands.
• The pending transaction list is paginated: 50 rows by default, 200 at most.

#What the screen refuses

• No vault configured: "No multi-sig configured for your brand", followed by an invitation to contact your SealTrust administrator.
• Transaction outside the account's scope: "Access denied to this transaction".
• Transaction that does not exist: "Pending transaction not found".
• Confirmation phrase missing or wrong: the broadcast is refused before any call to the chain. Same refusal for a two-factor code that is missing, invalid or not enrolled.
• Phrase unreadable on the server side: "Could not read the sentence to retype from the server, so nothing was sent."
• No transaction to show: "No pending transactions" or "No transactions", depending on the filter.