Scope: Low-impact, routine, or housekeeping decisions that do not materially affect the protocol’s security, contract architecture, or strategic direction. Examples include: small bug bounty payments (e.g. $1,000), minor operational expenditures, cosmetic parameter updates, non-controversial administrative actions, answering to a short term RFP, etc.
| Parameter | Value |
|---|---|
| Forum debate period | 24 hours |
| Voting period | 24 hours |
| Debate and vote | Concurrent (debate and vote run in parallel) |
| Quorum | 30% of total vlSDT supply |
| Approval threshold | Simple majority (>50% of votes cast, excl. abstentions) |
| Anticipated execution | If super-quorum is reached |
Process:
- Proposal posted simultaneously on the governance forum and Snapshot.
- The forum post must clearly indicate why the proposal qualifies as minor impact.
- Debate and voting run concurrently for 24 hours.
- The elevated quorum (30%) compensates for the shortened timeline, ensuring that even fast-tracked minor decisions have sufficient community awareness.
- If quorum is reached and the proposal achieves a simple majority, the DAO Multisig may execute.
Scope limitation: If a community member challenges the classification of a proposal as “minor impact” during the debate period, and the challenge is supported by substantive arguments, the proposer should consider withdrawing and resubmitting under Category A (SDGP).
Materiality Threshold:
A proposal shall not qualify as “Minor Impact” if it:
-
Affects smart contract logic;
-
Impacts user funds or risk parameters;
-
Introduces new integrations or counterparties;
-
Exceeds a threshold of $20,000.
In case of doubt, the proposal must default to Category A.