Labels: documentation 200pts
Background:
Spending limits (daily, weekly) and the circuit breaker are critical security features. There is no user-facing guide explaining how to configure them, what values to use, or how to respond when a limit is hit.
Problem:
DAO operators don't know: what spending limit values are appropriate, how to calculate limits based on treasury size, what happens when a limit is hit, how to temporarily raise limits for large operations, or how to use the compliance score to assess limit effectiveness.
What "Done" Looks Like:
- New
docs/guides/TREASURY_RISK_MANAGEMENT.md
- Spending limit setup guide: recommended values as percentages of treasury size (e.g., daily limit = 5% of total balance)
- "What happens when a limit is hit" — end-user experience, contract error, recovery steps
- Temporary limit raise procedure: governance proposal process, suggested timelock, post-operation reset
- Circuit breaker configuration: choosing the right threshold, testing the circuit breaker in staging
- Compliance score interpretation: what score means the treasury is "healthy" and what triggers concern
- Monthly risk review checklist: items to review, how to generate the compliance report
Key Files to Reference:
contracts/vault/src/lib.rs (spending limit functions)contracts/vault/src/storage.rs (Temporary storage for limits)frontend/src/components/SpendingLimitsPanel.tsxfrontend/src/components/ComplianceReports.tsx
Constraints:
- Percentage recommendations must be clearly labeled as "guidelines, not mandates"
- Circuit breaker section must reference the actual
Config.circuit_breaker_threshold field
- Monthly checklist must be actionable in under 1 hour
PR Must Include:
docs/guides/TREASURY_RISK_MANAGEMENT.md (min 2000 words)- Spending limit calculator table
- Monthly risk review checklist (formatted as a Markdown checklist)
Labels:
documentation200ptsBackground:
Spending limits (daily, weekly) and the circuit breaker are critical security features. There is no user-facing guide explaining how to configure them, what values to use, or how to respond when a limit is hit.
Problem:
DAO operators don't know: what spending limit values are appropriate, how to calculate limits based on treasury size, what happens when a limit is hit, how to temporarily raise limits for large operations, or how to use the compliance score to assess limit effectiveness.
What "Done" Looks Like:
docs/guides/TREASURY_RISK_MANAGEMENT.mdKey Files to Reference:
contracts/vault/src/lib.rs(spending limit functions)contracts/vault/src/storage.rs(Temporary storage for limits)frontend/src/components/SpendingLimitsPanel.tsxfrontend/src/components/ComplianceReports.tsxConstraints:
Config.circuit_breaker_thresholdfieldPR Must Include:
docs/guides/TREASURY_RISK_MANAGEMENT.md(min 2000 words)