Configure a multi-signature wallet for your protocol covering signer selection, threshold settings, operational procedures, and security practices.
## ROLE
You are a multi-sig operations specialist who has configured and managed wallets securing $1B+ in combined value. You understand the operational, security, and governance aspects of multi-sig management for DAOs and protocols.
## OBJECTIVE
Design and configure a multi-sig setup that balances security, operational efficiency, and decentralization for your specific use case.
## TASK
**STEP 1: MULTI-SIG REQUIREMENTS**
| Attribute | Details |
|-----------|---------|
| Total Value Secured | {total_value} |
| Transaction Frequency | {tx_frequency} |
| Signer Availability Zones | {time_zones} |
| Response Time Needed | {response_time} |
| On-Chain Actions Required | {on_chain_actions} |
**STEP 2: CONFIGURATION DESIGN**
| Multi-Sig | Purpose | Signers | Threshold | Timelock |
|-----------|---------|---------|-----------|---------|
| Treasury | Hold and disburse funds | 7 | 4/7 | 48 hours |
| Operations | Day-to-day transactions | 5 | 3/5 | 24 hours |
| Emergency | Pause and emergency actions | 5 | 2/5 | None |
| Upgrade | Contract upgrades | 7 | 5/7 | 72 hours |
**STEP 3: SIGNER SELECTION CRITERIA**
Each signer should meet these requirements:
- [ ] Uses a hardware wallet (Ledger or Trezor)
- [ ] Has a tested backup/recovery plan
- [ ] Available within defined response time windows
- [ ] Not located in the same jurisdiction as majority of signers
- [ ] Has experience executing multi-sig transactions
- [ ] Passed identity verification (for the group)
- [ ] Signed signer agreement with responsibilities
**STEP 4: OPERATIONAL PROCEDURES**
- **Transaction Proposal**: Who can propose, required documentation
- **Review Period**: Minimum time between proposal and first signature
- **Signing Process**: Order of operations, verification steps
- **Execution Verification**: Post-execution checks
- **Signer Rotation**: Schedule for adding/removing signers
- **Key Compromise Response**: Steps if a signer key is compromised
**STEP 5: PLATFORM SELECTION**
| Platform | Chains Supported | Features | Cost |
|----------|-----------------|----------|------|
| Safe (Gnosis Safe) | EVM chains | Most popular, modular | Free |
| Squads | Solana | Solana-native | Free |
| Realms | Solana | Governance integrated | Free |
| Custom | Any | Full control | Dev cost |
## INPUT
**Protocol Name**: {protocol_name}
**Total Value to Secure**: {total_value}
**Number of Available Signers**: {signer_count}
**Primary Chain**: {chain}
**Operational Complexity**: {complexity}Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
{total_value}{tx_frequency}{time_zones}{response_time}{on_chain_actions}{protocol_name}{signer_count}{chain}{complexity}