teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 3 Projects Releases Packages Wiki Activity Actions 2
teleo-codex/entities/internet-finance/sanctum-cloud-staking-active-rewards.md
Teleo Agents 623a26696a rio: extract from 2025-02-06-futardio-proposal-should-sanctum-implement-cloud-staking-and-active-staking-re.md 
- Source: inbox/archive/2025-02-06-futardio-proposal-should-sanctum-implement-cloud-staking-and-active-staking-re.md
- Domain: internet-finance
- Extracted by: headless extraction cron (worker 5)

Pentagon-Agent: Rio <HEADLESS>
2026-03-12 05:40:51 +00:00

4.2 KiB
Raw Blame History

type entity_type name domain status parent_entity platform proposal_number proposal_account proposer proposal_url discussion_url proposal_date resolution_date autocrat_version category summary tracked_by created
entity decision_market Sanctum: Should Sanctum implement CLOUD staking and active staking rewards? internet-finance passed sanctum futardio CLOUD-1 4BTTxsV98Rhm1qjDe2yPdXtj7j7KBSuGtVQ6rUNWjjXf proPaC9tVZEsmgDtNhx15e7nSpoojtPD3H9h4GqSqB2 https://www.futard.io/proposal/4BTTxsV98Rhm1qjDe2yPdXtj7j7KBSuGtVQ6rUNWjjXf https://research.sanctum.so/t/cloud-1-should-sanctum-implement-cloud-staking-and-active-staking-rewards/1228 2025-02-06 2025-02-09 0.3 mechanism Implement CLOUD staking with 30-day vesting lockup and allocate 30M CLOUD (3% supply) to active staking rewards rio 2026-03-11

Sanctum: Should Sanctum implement CLOUD staking and active staking rewards?

Summary

Sanctum's first governance proposal (CLOUD-1) passed on 2025-02-09, implementing two mechanism innovations: (1) CLOUD staking with 30-day linearly vesting lockup to filter for long-term holders and mitigate Keynesian beauty contest dynamics in futarchy markets, and (2) active staking rewards allocating 30M CLOUD (3% of total supply) to compensate governance participation based on (staked amount × time) × vote count.

The proposal explicitly frames staking lockups as a solution to futarchy's "primary potential failure mode"—traders predicting what others think rather than actual value. Distribution occurs quarterly over six months (two 15M CLOUD tranches), with minimum 10 USDC trading volume per proposal required to count as participation.

Market Data

  • Outcome: Passed
  • Proposal Account: 4BTTxsV98Rhm1qjDe2yPdXtj7j7KBSuGtVQ6rUNWjjXf
  • DAO Account: 5n61x4BeVvvRMcYBMaorhu1MaZDViYw6HghE8gwLCvPR
  • Proposer: proPaC9tVZEsmgDtNhx15e7nSpoojtPD3H9h4GqSqB2
  • Autocrat Version: 0.3
  • Proposal Date: 2025-02-06
  • Resolution Date: 2025-02-09

Key Mechanism Parameters

  • Staking lockup: 30-day linear vesting (~3.3 CLOUD/day per 100 sCLOUD unstaked)
  • Active staking rewards: 30M CLOUD (3% total supply)
  • Distribution: Two 15M CLOUD tranches, quarterly
  • Participation threshold: 10 USDC minimum trading volume per proposal
  • Proposal cadence: Every two weeks (1 week deliberation + 3 day voting)
  • Market transition: Deferred move from CLOUD/USDC to sCLOUD/USDC "whilst governance is still new and confusing"

Significance

This proposal is significant for futarchy mechanism design in three ways:

  1. Beauty contest mitigation: First production implementation of staking lockups explicitly designed to filter market participants by time horizon, addressing Robin Hanson's original concern about momentum trading in conditional markets.

  2. Participation incentives: Tests whether paying for governance engagement (3% of supply over six months) increases decision quality or just attracts noise traders. The staking score × vote count formula rewards both capital commitment and active participation.

  3. Adoption friction acknowledgment: The proposal's decision to defer sCLOUD/USDC markets because users find futarchy "new and confusing" reveals that even committed projects must phase mechanism complexity, contradicting the assumption that futarchy can be adopted wholesale.

Sanctum is a major Solana LST protocol, making this a test case for whether established projects (not just new launches) can successfully adopt futarchy governance.

Relationship to KB