Governance
SUDIGITAL follows a progressive decentralization model — starting with multisig security, transitioning through snapshot voting, and arriving at full on-chain DAO governance.
Where it actually stands (2026-11-04): Phase 1 only. The multisig exists and holds the program upgrade authority; no governance program, proposal system, snapshot space or token vote exists in the repository. Phase 2 and Phase 3 below are design, and a phase starts when its dates and mechanism are published on this page — not when the calendar passes a milestone.
Progressive Decentralization
Phase 1: Multi-Sig Safe (active since 2026-07-18)
| Property | Value |
|---|---|
| Authority | 6-of-7 team multisig |
| EVM | Gnosis Safe on Base |
| Solana | Squads v4 multisig |
| Squads Address | 3Wt7pitDH9ufwpsYwnbbYhYWXZqsGWNqmZRUgHQXa5Z4 |
| Squads Vault | 3EkpyVQAzFSynkxCfDJKUp2YdUEPG2H63hZZU4vsbwFx |
| Safe Address | 0xb0599ce3595Ed3768B08B9B4e7d96AF309a7f49a |
| Decisions | Emergency changes, parameter tuning |
| Transparency | All decisions published |
The multisig requires 6 of 7 members to approve any transaction it signs. It holds the program upgrade authority on Solana and the whole Safe on Base; the Solana program-level admin roles (WALLET_CREATOR, treasury, pool, ecosystem, backend_authority) are a single key today, so "6 of 7 approves every administrative operation" overstates Phase 1 — see Multisig Governance.
Phase 2: Snapshot Governance (design — not started)
| Property | Value |
|---|---|
| Authority | SUDIGITAL token holder voting |
| Decisions | Fee parameters, emissions, partnerships |
| Quorum | 4% of circulating supply |
| Approval | 51% majority |
The intended mechanism: token holders vote on proposals via off-chain snapshot voting, and results are executed by the multisig. Nothing of it is built — no snapshot space, no proposal record, no vote.
Phase 3: On-Chain DAO (design — no date)
| Property | Value |
|---|---|
| Authority | SPL Governance (Solana native) |
| Decisions | All protocol parameters, treasury |
| Quorum | 10% of circulating supply |
| Approval | 60% supermajority |
Design: full on-chain governance with executable proposals stored on-chain, at which point the multisig transfers authority to the DAO program.
DAO Structure (design)
- Token holders vote directly on proposals
- NFT holders carry a 2x reward multiplier in the economy program; no voting multiplier exists — a voting bonus would need a new program
- Multi-day voting period — transparent and accessible across time zones
- Executable proposals — approved proposals execute automatically on-chain
- Timelock — 1-30 day delay between approval and execution for security
The EVM Security.TimelockOp timelock above is real and deployed; everything else in this section is the target design.
Governance Scope
| Category | Phase 1 (live) | Phase 2 (design) | Phase 3 (design) |
|---|---|---|---|
| Emergency pause | Yes | Yes | Yes |
| Fee parameters | Yes | Yes | Yes |
| Emission rates | Yes | Vote | Vote |
| Burn parameters | Yes | Vote | Vote |
| Treasury spending | Yes | Advisory | Vote |
| Contract upgrades | Yes | Advisory | Vote |
| New chain deployment | Yes | Advisory | Vote |
| Protocol parameters | Yes | Vote | Vote |
On-Chain Security
Timelock (EVM)
All significant operations go through a timelock:
| Parameter | Value |
|---|---|
| Min Delay | 1 day |
| Max Delay | 30 days |
| Operations | Schedule, execute (after delay), cancel |
Upgrade Authority
- EVM: UUPS proxy pattern — the Safe (6-of-7) is the upgrader
- Solana: Anchor upgradeable — the upgrade authority is the Squads vault, transferred 2026-07-18 when the programs deployed to mainnet-beta
Platform Config
The CoreModule / sudigital-core manages platform-level authority:
| Function | Description |
|---|---|
initializePlatformConfig(backendAuthority) | Set trusted backend signer |
updateBackendAuthority(newAuthority) | Rotate backend signing key |
setPlatformActive(isActive) | Emergency kill switch |
Team Alignment
Team tokens are locked to ensure long-term alignment:
| Parameter | Value |
|---|---|
| Team Allocation | 10% (100,000,000 tokens) |
| Cliff | 12 months (no tokens released) |
| Vesting | 48 months total (linear after cliff) |
| Revocable | EVM: yes (by authority). Solana: no — sudigital-vesting has no revoke instruction |
This means team members receive zero tokens for the first year, then linear release over the remaining 3 years. The clock starts when a vesting stream is created, so nothing is claimable today and the first unlock is 12 months after that stream starts.
Related
- Roadmap — governance timeline
- Blockchain Security — multisig and audit details
- Staking & Rewards — governance-controlled parameters