2.1 Purpose
This policy establishes secure procedures for managing cryptocurrency wallets and treasury assets, ensuring proper controls, accountability, and protection of organizational funds.
2.2 Wallet Structure
2.2.1 Multi-Signature Requirements
All organizational wallets must use multi-signature (multi-sig) security:
- Primary Treasury Wallet: [X of Y] signatures required (e.g., 3 of 5)
- Operational Wallet: [X of Y] signatures required for day-to-day transactions
- Receiving Wallet: [X of Y] signatures required
2.2.2 Authorized Signers
| Role |
Name |
Wallet Access |
Backup |
| [Title] |
[Name] |
[Which wallets] |
[Backup signer] |
| [Title] |
[Name] |
[Which wallets] |
[Backup signer] |
2.3 Hardware Wallet Requirements
- All signers must use hardware wallets (e.g., Ledger, Trezor) for signing transactions
- Hardware wallets must be purchased directly from manufacturers
- Multi-factor authentication must be enabled on all associated accounts
2.4 Seed Phrase Management
Critical Security Requirements:
- Seed phrases must NEVER be stored digitally (no photos, documents, or cloud storage)
- Physical copies must be stored in at least [two/three] secure locations:
- [e.g., Bank safe deposit box]
- [e.g., Fireproof safe at secure location]
- Access to seed phrase locations limited to: [list authorized individuals]
2.5 Transaction Approval Process