Members and permissions
Members are the human or system authorities behind a multisig. Each member has an identity scheme and a set of permissions.
Member identity types
| Scheme | Typical reason to use |
|---|---|
| Ed25519 | Solana-native operators, fee payers, and continuity with existing wallets. |
| Secp256k1 | EVM-native council members or cross-chain governance participants. |
| Falcon-512 | Repeated compact post-quantum approvals. |
| Winternitz | Hash-based post-quantum approval with one-time state discipline. |
Permission model
Permissions can separate operational roles:
- Initiate: create proposals.
- Vote: approve or reject proposals.
- Execute: submit approved actions.
- Settings: participate in governance changes where required by policy.
Rotation practices
Rotate members through settings proposals rather than creating a new vault. The goal is stable governed addresses with changing signer policy.
Non-member viewing
The app may display a multisig to a connected wallet that is not a member. Non-members can inspect public state but should not see action controls that require member authority.