Committee payout
Propose a transfer, collect M approvals, finalize - no one machine holds the spending key.
Knot
Shared control. Keys stay on your machines.
Form an M-of-N council, propose an intent, collect approvals to threshold, then finalize - keys never leave the members' machines.
Docs
You: -
Approvals -
Beat 1 · Cast
Meet the cast
Named BLS keys stay in this process. Click a member to use them on later beats.
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, 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 at threshold.
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 councils are for
Same M-of-N rails - different jobs.
Dispute council
Fingerprint-bound council resolve for contested outcomes - shared authority without a single adjudicator.
Keys stay local
Named identities live in this Lab session. When you run the real tool binary, signing stays in-process - the server never sees a secret key.