Create a multisig
Creating a multisig establishes the governed account, initial members, threshold rules, and optional timelock. The address is intended to remain stable while the membership evolves through later settings proposals.
Creation checklist
- Name the multisig for local operator clarity.
- Select the fee payer.
- Add initial members.
- Assign member permissions.
- Set
threshold. - Set
pq_threshold. - Set a timelock if high-value actions should wait before execution.
- Review the final member and policy summary.
Member identities
Each member row points to one identity:
- Ed25519 for Solana-native continuity.
- Secp256k1 for EVM-compatible signers.
- Falcon-512 for compact recurring post-quantum approval.
- Winternitz for hash-based one-time approval.
Thresholds
threshold is the total number of approvals required. pq_threshold is the number of approvals that must come from Falcon or Winternitz members. pq_threshold cannot be greater than the number of available post-quantum members or greater than the total threshold.
Initial policy examples
| Policy | Good for |
|---|---|
| 1-of-1 Falcon | Personal test vaults and simple devnet demos. |
| 2-of-3 Ed25519/Falcon mix | Teams learning PQ approval without losing classical continuity. |
| 3-of-5 including 1 PQ | Treasuries starting staged migration. |
| 3-of-5 including 2 PQ | Stronger policies after operators are comfortable. |
Do not use production seed phrases or production custody keys while the app is in devnet mode.