Multi-Sig Treasury Skill
Gnosis Safe and multisig treasury management for DAOs, protocols, and crypto-native
organizations. Covers setup, monitoring, governance, and financial health reporting.
When to Use This Skill
Use when:
- - Setting up a new Gnosis Safe (mainnet, L2, or testnet)
- Monitoring treasury balances across chains
- Generating spending proposals or transaction templates
- Auditing signer activity and threshold compliance
- Producing treasury health dashboards for stakeholders
- Configuring alerts for low runway or spending anomalies
- Managing signer rotation (add/remove owners, change threshold)
- Preparing DAO governance documentation around treasury actions
Do NOT use when:
- - Managing individual wallets or personal portfolios (use a wallet tracker)
- Auditing Solidity contracts for security (use
solidity-audit-precheck) - Calculating crypto taxes or cost basis (use
crypto-tax-agent) - Executing live on-chain transactions (always require human approval)
- Assessing DeFi yield or LP positions (use
defi-position-tracker)
Core Capabilities
1. Safe Setup & Configuration
New Safe deployment checklist:
CODEBLOCK0
Recommended thresholds by org size:
| Org Size | Signers | Threshold | Rationale |
|---|
| Small team <5 | 3 | 2-of-3 | Fast execution, basic protection |
| Mid team 5-15 |
5 | 3-of-5 | Balanced speed vs security |
| Large DAO | 7-9 | 4-of-7 | Resilient to key loss |
| Protocol core | 9+ | 5-of-9 | Maximum governance legitimacy |
Signer best practices:
- - Hardware wallets only for signers (Ledger, Trezor)
- No exchange wallets or custodial keys as signers
- Geographic/timezone distribution for 24h coverage
- Documented succession plan for key rotation
- Test signing every 90 days to confirm access
2. Treasury Health Dashboard
Key metrics to track:
CODEBLOCK1
Stablecoin ratio target: Maintain 40-60% in stablecoins. Below 30% = risk flag.
Runway tiers:
- - 🟢 >18 months: Healthy — can deploy capital
- 🟡 12-18 months: Caution — review burn rate
- 🟠 6-12 months: Raise flag — begin fundraising
- 🔴 <6 months: Critical — emergency protocol
3. Spending Proposal Templates
Standard payment proposal:
CODEBLOCK2
Budget categories for DAO treasuries:
STANDARD GL CODES — DAO TREASURY
─────────────────────────────────────────────
100 - Core Contributors (salaries/grants)
110 - Contractor Payments
120 - Bounties & Community Rewards
200 - Infrastructure & DevOps
210 - Security Audits
220 - Protocol Tooling & Licenses
300 - Marketing & Community
310 - Events & Conferences
320 - Grants Program
400 - Legal & Compliance
500 - R&D / Grants Received (offset)
900 - Miscellaneous / Under Review
4. Signer Management & Rotation
Adding a signer:
CODEBLOCK4
Removing a signer (compromised or offboarded):
CODEBLOCK5
Threshold change formula:
- - Ideal threshold = floor(N * 0.6) where N = signer count
- Never go below 2 (defeats multisig purpose)
- Never require ALL signers (one lost key = frozen funds)
5. Alert Configuration
Spending threshold alerts:
CODEBLOCK6
Monitoring services:
- - Tenderly Alerts — on-chain tx monitoring, free tier available
- Safe Webhook — native notifications for queued/executed txs
- OpenZeppelin Defender — advanced monitoring + automated responses
- Hal.xyz — no-code blockchain alerts, good for non-technical signers
- Dune Analytics — custom dashboards for public-facing reporting
6. Multi-Chain Treasury Tracking
Chain inventory template:
CODEBLOCK7
Consolidation policy:
- - Keep 90-day operating budget on L2s, rest on mainnet
- Bridge USDC only via canonical bridges (Circle CCTP preferred)
- Never bridge governance tokens cross-chain without vote
- Document all bridge transactions with on-chain references
7. Governance Integration
Snapshot + Safe integration pattern:
- 1. Create Snapshot proposal with treasury action
- Attach Safe transaction hash to proposal
- Voting passes → 3-day timelock (recommended)
- Signers execute after timelock expires
- Link on-chain tx to Snapshot proposal in comments
Governor contract pattern (fully on-chain):
- - OpenZeppelin Governor + TimelockController
- Safe as execution target for governor
- See
develop-secure-contracts skill for Governor setup
Safe Modules for governance:
- -
SafeSnap (Gnosis) — connects Snapshot directly to Safe execution - INLINECODE5 — optimistic governance via oracle
- INLINECODE6 — mandatory timelock on all transactions
Example Workflows
Workflow A: New DAO Treasury Setup
CODEBLOCK8
Workflow B: Monthly Treasury Report
CODEBLOCK9
Workflow C: Emergency Signer Compromise
CODEBLOCK10
Tool Stack
| Tool | Use | URL |
|---|
| Safe UI | Deploy, execute, manage signers | app.safe.global |
| Safe API |
Pull balances and transaction history | safe-transaction-service API |
| Tenderly | On-chain alerts and simulations | tenderly.co |
| Gnosis Safe CLI | Scripted Safe management | github.com/gnosis/safe-cli |
| Dune Analytics | Public treasury dashboards | dune.com |
| Hal.xyz | No-code blockchain alerts | hal.xyz |
| Debank Pro | Multi-chain portfolio view | debank.com |
| Etherscan/Arbiscan | Transaction verification | etherscan.io / arbiscan.io |
Quick Reference: Safe API
CODEBLOCK11
Related Skills
- -
develop-secure-contracts — for Governor + TimelockController on-chain governance - INLINECODE8 — cost basis and tax reporting for treasury assets
- INLINECODE9 — monitoring DeFi yield from treasury-deployed capital
- INLINECODE10 — if deploying custom treasury contracts
- INLINECODE11 — general Ethereum development reference
多重签名金库技能
面向DAO、协议及加密原生组织的Gnosis Safe与多重签名金库管理。涵盖设置、监控、治理及财务健康报告。
何时使用此技能
适用场景:
- - 设置新的Gnosis Safe(主网、L2或测试网)
- 监控跨链金库余额
- 生成支出提案或交易模板
- 审计签名人活动及阈值合规性
- 为利益相关者制作金库健康仪表盘
- 配置低资金跑道或异常支出警报
- 管理签名人轮换(添加/移除所有者,更改阈值)
- 围绕金库操作准备DAO治理文档
不适用场景:
- - 管理个人钱包或个人投资组合(请使用钱包追踪器)
- 审计Solidity合约安全性(请使用solidity-audit-precheck)
- 计算加密货币税务或成本基础(请使用crypto-tax-agent)
- 执行实时链上交易(始终需要人工审批)
- 评估DeFi收益或LP头寸(请使用defi-position-tracker)
核心能力
1. Safe设置与配置
新Safe部署清单:
SAFE设置清单
─────────────────────────────────────────────
□ 确定签名人数量及阈值(M-of-N)
□ 收集签名人钱包地址 + ENS名称
□ 选择部署链 — 主网 / L2
□ 通过app.safe.global或Safe CLI部署
□ 在区块浏览器上验证合约地址
□ 在金库注册表中记录Safe地址
□ 转移真实资金前先进行小额交易测试
□ 设置通知(Safe webhook或Tenderly)
按组织规模推荐的阈值:
| 组织规模 | 签名人 | 阈值 | 理由 |
|---|
| 小型团队 <5 | 3 | 2-of-3 | 快速执行,基本保护 |
| 中型团队 5-15 |
5 | 3-of-5 | 速度与安全性平衡 |
| 大型DAO | 7-9 | 4-of-7 | 对密钥丢失具有弹性 |
| 协议核心团队 | 9+ | 5-of-9 | 最大治理合法性 |
签名人最佳实践:
- - 签名人仅使用硬件钱包(Ledger、Trezor)
- 不使用交易所钱包或托管密钥作为签名人
- 地理/时区分布以实现24小时覆盖
- 记录密钥轮换的继任计划
- 每90天测试签名以确认访问权限
2. 金库健康仪表盘
需追踪的关键指标:
金库健康快照 — [日期]
══════════════════════════════════════════════════════
Safe地址: 0x1234...abcd
网络: Ethereum主网 | Arbitrum | Base
─────────────────────────────────────────────────────
余额
ETH: 142.3 ETH ($427,000)
USDC: $1,240,000
DAI: $380,000
协议代币: 2,400,000 TKN ($960,000)
─────────────────────────────────────────
总计(美元): $3,007,000
资金跑道分析
月度支出: $85,000/月(近3个月平均值)
稳定币: $1,620,000 → 19.1个月
总计(流动):$3,007,000 → 35.4个月
风险指标
✅ 资金跑道 > 12个月
✅ 稳定币占金库比例 > 50%
⚠️ ETH >25% — 监控价格敞口
✅ 无待领取的协议奖励
✅ 所有签名人近90天内活跃
近期活动(最近30天)
交易: 12笔已执行,0笔待处理
最大交易: $45,000 USDC(贡献者付款)
阈值: 3-of-5(全部满足)
══════════════════════════════════════════════════════
稳定币比例目标: 保持40-60%的稳定币。低于30% = 风险标志。
资金跑道等级:
- - 🟢 >18个月:健康 — 可部署资金
- 🟡 12-18个月:谨慎 — 审查支出率
- 🟠 6-12个月:发出警报 — 开始募资
- 🔴 <6个月:危急 — 紧急协议
3. 支出提案模板
标准付款提案:
markdown
金库提案:[标题]
日期: YYYY-MM-DD
Safe: 0x1234...abcd
提交人: [贡献者 / DAO用户名]
请求类型: [ ] 一次性 [ ] 定期 [ ] 基于里程碑
摘要
[一段话:什么、为什么、为谁]
金额
- - 代币:USDC / ETH / DAI / 其他:
- 金额:$
- 收款地址:0x
- ENS(如适用):_.eth
交付物 / 理由
- 1. [交付物 1]
- [交付物 2]
- [交付物 3]
链接
- - 范围文档:[URL]
- 先前工作:[URL]
- 论坛讨论:[URL]
时间线
- - 预计完成时间:[日期]
- 付款触发条件:[完成时 / 预付款 / 里程碑]
风险 / 备注
[任何相关风险标志或依赖项]
所需签名人:[M] of [N]
DAO金库预算类别:
标准总账代码 — DAO金库
─────────────────────────────────────────────
100 - 核心贡献者(薪资/资助)
110 - 承包商付款
120 - 赏金与社区奖励
200 - 基础设施与DevOps
210 - 安全审计
220 - 协议工具与许可证
300 - 市场营销与社区
310 - 活动与会议
320 - 资助计划
400 - 法律与合规
500 - 研发/已收资助(抵消)
900 - 杂项/审查中
4. 签名人管理与轮换
添加签名人:
签名人添加清单
─────────────────────────────────────────────
□ 确认新签名人的钱包地址
□ 验证签名人拥有密钥(签名消息测试)
□ 确认使用硬件钱包
□ 通过Safe UI投票/提案:添加所有者
□ 达到当前签名人阈值以批准
□ 如有需要更新阈值(建议M+1)
□ 在金库注册表中记录
□ 向DAO治理论坛公告
□ 48小时内与新签名人进行交易测试
移除签名人(遭入侵或离职):
签名人移除 — 紧急协议
─────────────────────────────────────────────
□ 不要向遭入侵的签名人透露意图
□ 私下召集剩余签名人
□ 通过Safe UI排队移除所有者交易
□ 在遭入侵签名人能够转移资金前执行
□ 可选择立即将资金转移至新Safe
□ 审查所有待处理交易是否存在后门
□ 轮换任何共享机密(API密钥等)
□ 24小时内进行事后文档记录
阈值变更公式:
- - 理想阈值 = floor(N * 0.6),其中N = 签名人数
- 切勿低于2(违背多重签名目的)
- 切勿要求所有签名人(丢失一个密钥 = 资金冻结)
5. 警报配置
支出阈值警报:
yaml
金库警报阈值
alerts:
runway_months:
yellow: 12
red: 6
stablecoin_ratio:
yellow: 0.35 # 低于35%时警告
red: 0.20 # 低于20%时危急
single
txusd:
notify: 10000 # 标记任何超过$10k的交易
require_forum: 50000 # 超过$50k需要论坛帖子
inactive
signerdays: 90
pending
txhours: 72 # 交易待处理超过72小时时发出警报
监控服务:
- - Tenderly Alerts — 链上交易监控,提供免费套餐
- Safe Webhook — 排队/执行交易的原生通知
- OpenZeppelin Defender — 高级监控 + 自动响应
- Hal.xyz — 无代码区块链警报,适合非技术签名人
- Dune Analytics — 面向公众报告的自定义仪表盘
6. 多链金库追踪
链清单模板:
多链金库注册表
─────────────────────────────────────────────
主网Safe: 0x1234...abcd
↳ 余额: ETH, USDC, DAI, TKN
↳