1. Request For Comment (RFC) Process
RFCs are informal proposals to share ideas, get early feedback, and shape the direction of a future SIP (Summer Improvement Proposal).
- Post in the General Discussion > Request for Comment [RFCs] category with the
[RFC]prefix - Include problem + rationale + early solution outline
- Use this RFC Template to streamline your post
- Community feedback should be incorporated before promoting to SIP
- Tag @Recognized_Delegates for visibility
This is your chance to shape proposals collaboratively. RFCs can evolve quickly—don’t worry about being perfect at the start!
2. Summer Improvement Proposals (SIPs)
SIPs are formalized proposals intended for onchain voting.
- Post to the Governance > Summer Improvement Proposals [SIPs] category with
[SIP-X]title format - Must include: Abstract, Motivation, Specification, and Risks
- Use this SIP Template to streamline your post
- Proposals must meet security and feasibility standards. Summon @BlockAnalitica (by tagging them) to consult risk parameters
- Tag @Recognized_Delegates for visibility
Once posted, SIPs will undergo community review before moving to a Tally vote.
3. Onchain Voting via Tally
All finalized proposals are voted onchain via Tally.
- Voting Period: 3 days
- Proposal Delay: 1 day (Base) + 1 day (Other Chains)
- Proposal Threshold: 10k SUMR
- Quorum needed: 144.02M SUMR
- Delegates and token holders can vote or abstain
- Signal participation matters—track delegate responsiveness in the dashboard
Delegate? Reach out to @techsqrt to map your identity to the dune dashboard and get visibility in governance metrics.
