@
DAO Governance That Executes Itself
A vote passes → Lighthouse validates the result → the protocol pulls and forwards. No multisig coordination per transaction. The multisig approves the policy; the protocol handles the rest.
Pitch of the Core Idea
DAOs manage billions in treasury assets but deploy them manually — multisig signers coordinate across time zones, each transaction requires quorum, urgency means someone gets paged at 3am. The DAO treasury management market is $0.7-0.8B in 2025, growing to $1.7-5.1B by 2030-2034 at 18-22% CAGR. Safe (Gnosis) secures $35B+ with 63M+ accounts. Yet treasury capital sits underutilized, yield opportunities missed, and funding decisions take days to execute.
Tributary v1 turns governance decisions into automated execution policies. Governance votes: “Deploy 30% of idle USDC into Kamino, 20% into Meteora LP.” Lighthouse validates the vote passed. Protocol executes the allocation. Treasury capital deploys in minutes, not days.
Core Mechanics
- DAO configures ComposablePolicy instances linked to governance outcomes
- Pre-validation (Lighthouse) — Evaluates governance state:
- Did proposal X pass with required quorum? (checks Realms/SPL Governance state)
- Has milestone condition been met? (checks on-chain deliverable attestation)
- Is allocation rebalance threshold triggered? (checks oracle/TVL data)
- Pull (Token Delegation) — Claims treasury funds from DAO’s token account (Squads multisig vault)
- Forward (CPI) — Routes to approved destination: SPL transfer, Jupiter swap, Kamino deposit, Meteora LP
WHEN (condition: Governance Proposal #42 executed on Realms)
→ VALIDATE (Lighthouse: assert proposal #42 state == Executed)
→ PULL ($50,000 USDC from DAO treasury vault)
→ FORWARD 1: $40,000 → grant recipient wallet (SPL transfer)
→ FORWARD 2: $10,000 → Kamino yield vault (CPI deposit)
Psychological Hook and Addictiveness
“Our treasury deploys itself.” The transformation from “DAO votes, then waits days for multisig to execute” to “DAO votes, treasury executes in minutes.” Governance becomes tangible — proposals don’t just pass, they do something immediately.
Real-time treasury visibility: Dashboard showing every policy, every execution, every yield earned. Grant milestone tracking: Transparent, automated milestone-based funding. Contributor payroll automation: Recurring payments without multisig approval per cycle.
Brief Market Research
| Metric | Data |
|---|---|
| DAO Treasury Market (2025) | $0.7-0.8B |
| Projected (2030) | $1.7B |
| Projected (2034) | $5.1B |
| CAGR | 18-22% |
| Safe Accounts | 63M+ |
| Safe AUM | $35B+ |
Key Competitors:
- Safe/Gnosis: Dominant multisig, $35B+ secured, but no automation
- Coinshift: Mid-market DAO treasury, streamlined interfaces
- Karpatkey: On-chain asset management for DAOs, treasury optimization
- Tally: DAO governance dashboard, but no automated execution
- Parcel: DAO payments and treasury, but limited automation
None link governance votes directly to automated treasury execution via Lighthouse validation.
Business Model
- Platform fee: 0.5-2% of treasury AUM annually
- Execution fee: 0.1-0.5% on each governance-triggered treasury movement
- Enterprise tier: $500-2,000/mo for custom governance integration
- Yield optimization: 10-20% of improved yield from automated allocation
- Compliance reporting: $200-1,000/yr for audit-ready treasury reports
Summary of Technical Specifications
Architecture
- Governance monitor (watches Realms/SPL Governance proposal state)
- Lighthouse validation layer (asserts governance conditions)
- Treasury policy engine (ComposablePolicy per governance outcome)
- Token delegation system (pull from multisig vault)
- Forward CPI routing (multi-destination execution)
- Dashboard (proposal tracking, execution history, yield reporting)
How This Hooks Into Tributary
- Milestone: Milestone-based grant funding releases
- Subscription: Recurring contributor payroll, operational expenses
- PayAsYouGo: Dynamic treasury movements based on governance
- Lighthouse: Validates governance state before execution
- Forward: CPI to approved destinations
Recommended Tech Stack
- Solana + Anchor
- Tributary SDK (Milestone + Lighthouse + Forward)
- Squads integration for multisig
- Realms/SPL Governance for proposal state
- Pyth/Switchboard for yield/TVL data
- React dashboard
MVP Scope
- Basic governance monitoring (Realms proposal state)
- Simple policy: “If proposal X passes, transfer $Y to address Z”
- Squads multisig integration
- Basic execution dashboard
- Buildable in 3 days with Tributary v1 SDK + Squads
Non-Technological Requirements
- DAO partnerships: Need DAOs willing to pilot automated treasury management
- Squads integration: Deep integration with Squads multisig infrastructure
- Legal framework: Automated treasury execution may have fiduciary implications
- Governance education: DAOs need to understand policy-based vs. transaction-based treasury
- Security auditing: Treasury automation is high-value target
Potential Risks
- Governance attack: Attacker gains voting control, passes proposals triggering policies. Policy conditions act as secondary check
- Multisig key compromise: Root of trust. If signer keys compromised, attacker can delegate to malicious policies
- Oracle dependency for milestones: Lighthouse milestone checks depend on reliable attestation sources
- Governance velocity mismatch: Some DAOs have 7-14 day voting periods. Policies only execute after full governance cycle