Paying out together
Someone proposes a transfer, enough members sign, and it goes out. No single machine can spend on its own.
Knot
Shared control. Keys stay on your machines.
A group lists its members and how many must agree, for example 2 of 3. Someone proposes an action, members sign it on their own machines, and once enough have signed, the chain runs it. Nobody hands over a key.
This page is a mock: nothing here touches a chain. Knot itself runs on Dusk testnet and isn't audited yet.
Demo
Mock
Testnet only, not audited yet
You: -
Approvals -
Beat 1 · Cast
Meet the cast
These keys exist only in this page. Click a member to act as them in the next steps.
Beat 2 · Form council
Form a multisig account
Select members for an M-of-N set. Anyone may create the account - naming keys grants no special power.
Beat 3 · Look it up
Look up the council
Select a council from this demo run. Free reads confirm members, threshold, delay, and nonce - no gas.
Members
Beat 4 · Propose
Propose an intent
Pick a purpose and describe what the council should do. The mock chain call stays under the hood.
Purpose
Beat 5 · Finalize
Approve & finalize
Pick a proposal, confirm the intent, approve as each signer, then finalize. Delay > 0 queues until Execute.
Proposals
Review intent
Fingerprint
A short check-code for this proposal so co-signers can compare intent. In this Lab the digest is a simulated stand-in - not a production BIP39 fingerprint.
Approve as (one at a time)
Developer drawer (testnet only)
Quorum verify (unsafe UTF-8)
Arbitrary message demo — preview fingerprint, then submit with confirm. Prefer one signer per serve process.
Fingerprint
Rotate council (change_account)
Replace members/threshold — preview digest, then submit with confirm.
Fingerprint
What it is for
Anything that should happen only when enough people agree. You can add a wait after they agree.
A wait before it runs
After the group agrees, the call can wait a set number of blocks before it runs. During the wait, the group can cancel it, which takes the same number of signatures.
Keys stay local
Here the keys live in this page. With the real Lab on your machine, signing happens there too, and no server ever sees a secret key.