Safeguards (Hard Eligibility Rules)
Not Eligible for Expedited Track
- New Fleet (Vault) creation.
- New ARK onboarding/offboarding.
- Protocol contract upgrades.
- Governance parameter changes.
- Tokenomics changes.
- Changes affecting liquidation logic or risk engine.
- Treasury commitments exceeding defined cap.
- Long-term recurring funding (> 3 months).
These must go through RFC → SIP.
Eligible Criteria
An Expedited Proposal must:
- Be operational, administrative, or tactical in nature.
- Be reversible or low impact.
- Have clearly defined scope and execution.
- Not require new smart contract deployment.
- Stay under treasury cap.
Cap: ≤10% of treasury OR $50,000 equivalent (whichever is lower).
- Have no material risk to protocol solvency.
- Remain open for 48h mandatory review on the Forum.
- Include at least 1 of the following tags:
expedited/fast-track/time-sensitive
If >3 delegates (with highest VP) request escalation → it can convert into SIP before 48h review window finalizes.
Use this template to create an expedited (fast-track) proposal that will go to a DAO vote on Tally. XXXs should be a middle lane for low-risk, operational, time-sensitive decisions that don’t justify a full RFC → SIP lifecycle/timeline; but still require transparency.
Title:
[EXPX/X.Y] Title of Proposal Here
Replace
XandYwith the next EXP number, e.g.[EXP4/EXP4.1].
Use the above formatting when creating a new topic:
Select appropriate category, and add tags for improved searchability.
1. Overview:
1–2 sentence description of the action being requested.
2. Eligibility Confirmation:
The author must explicitly confirm:
* [ ] No new Vault (Fleet) creation
* [ ] No ARK onboarding/offboarding
* [ ] No smart contract upgrade
* [ ] No governance parameter change
* [ ] No protocol risk model modification
* [ ] Treasury request ≤ approved expedited cap
* [ ] Action is operational and/or reversible
If any box cannot be checked → proposal must go through SIP process.
3. Background & Rationale:
Explain:
- Why this needs to happen now?
- Why expedited treatment is appropriate?
- What happens if delayed?
Keep it concise but sufficient for @Recognized_Delegates to evaluate.
4. Specification:
Clearly outline:
- Exact action to be taken.
- Amount (if funds involved).
- Responsible execution party (multisig, contributor, etc.).
- Timeline.
- Any dependencies.
5. Risks & Mitigations:
Brief explanation of:
- Technical risk.
- Governance risk.
- Reputational risk.
- Why impact is limited?
Always tag @Recognized_Delegates and tag @BlockAnalitica if remotely risk-adjacent.
6. Voting:
Define what a “YES” and “NO” vote entails. Follow up with a comment under the topic with a direct link to a Tally vote upon publishing.
