Overview
A Controlled Multisig is a multisig with a set Config Authority. This allows the config authority to manipulate the Squad’s configuration without being subject to consensus, functioning as an admin.
Using a Controlled Multisig is not recommended for most use cases. Understand the tradeoffs before choosing this setup.
What is a Config Authority?
The configAuthority field in the Multisig account determines how configuration changes are made:
Autonomous vs Controlled
Autonomous Multisig (Recommended)
- Config changes go through normal proposal and voting process
- All members have input on membership and threshold changes
- Most secure for decentralized governance
- Set
configAuthority: null when creating
Controlled Multisig
- Config authority can make changes without voting
- Single point of control for configuration
- Useful for specific admin scenarios
- Set
configAuthority to a specific public key
When to Use a Config Authority
Consider a Controlled Multisig only when:
- A single admin needs absolute control over configuration
- C-level executive requires specific config control
- Regulatory requirements mandate admin override capabilities
- Rapid configuration changes are operationally necessary
Available Config Authority Instructions
When a multisig has a Config Authority, use these special instructions:
Security Considerations
See Also