Market-listing governance threshold
Sanctum's assessment for RD-F-072 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Adapted factor: applied to Infinity LST whitelist governance. LST program changes require majority vote from 11-member multisig (Jito, Jupiter, Laine, Mango, MRGN, Solblaze, SolanaFM, Sanctum, plus others). CLOUD token holders can participate in futarchy-based governance (vote.sanctum.so) on important decisions including LST selection. However, CLOUD governance for LST admission is nascent and not confirmed as a hard on-chain requirement; team/multisig retains operational approval authority. Yellow because governance sits between low-threshold (team multisig) and full-DAO (CLOUD futarchy) — the transition is in progress.
Sources #
- DocsCLOUD: The Sanctum Governance Token — Sanctum DocsSanctum CLOUD governance: CLOUD token holders vote on protocol decisions including LST selection; futarchy governance at vote.sanctum.soretrieved 2026-05-04
- Solana Compass — Sanctum ProjectSolana Compass Sanctum project page: 11-member multisig governance for LST program — Jito, Jupiter, Laine, Mango, MRGN, Solblaze, SolanaFM, Sanctum; no single party can unilaterally change programretrieved 2026-05-04
Methodology #
Classify the governance threshold required to list a new market as: permissionless / low-threshold (team multisig) / high-threshold (DAO vote) / no new listings.
See the full factor methodology and distribution across all protocols →