Use this template when sharing an early-stage idea with the community. RFCs are informal and non-binding but crucial for early input and iteration before becoming a SIP.
Title:
[RFC] Title of Proposal Here
Use this formatting when creating a new topic:
Select appropriate category, and add tags for improved searchability.
0. Baseline ARK Criteria:
@BlockAnalitica as the risk curator of the Lazy Summer Protocol, has shared the best practices for recommending new ARKs (strategies) to be added to the existing FLEETs (vaults).
Please, read through, consider and include this assessment in your proposal. This is only applicable to recommending/introducing new ARKs to the protocol.
1. Summary:
A brief, one-paragraph summary of what this RFC aims to solve or change. Think of this like a TL;DR.
Tag forum username(s) if the proposal is co-written.
2. Context & Motivation:
Why this RFC matters. What current problem, limitation, or opportunity is being addressed? Reference existing RFCs/SIPs, community discussions, or protocol parameters if relevant.
3. Proposal:
Describe your initial proposed solution, design, or direction. It’s okay if things are still in flux. This is where the community can help co-develop it. Include specifics where possible (e.g. affected parameters, changes to roles/processes).
4. Open Questions:
List any unresolved issues or items you’d like community input on. This is a great way to focus discussion.
5. Next Steps:
* Gather community feedback
* Iterate based on discussion
* Promote to SIP (with clear, formal specification)
6. Informal Support Indicator (*optional):
Based on the [RFC] posted by StableLab it is suggested to use a non-obligatory signal via polling as a way to gauge community sentiment.
