SIP TEMPLATE: Summer Improvement Proposal

Start Here Resources and Tutorials
, ,
1

Use this template to create a formal proposal that will eventually go to a DAO vote on Tally. SIPs should be finalized and reflect a well-considered design, ideally building on a prior RFC.

Title:

[SIPX.Y/SIPX.Y.Z] Title of Proposal Here

Replace X,Y, and Z with the next SIP number, e.g. [SIP2.16.1]

SIP Description
SIP0.Y Governance Process
SIP1.Y Vault (FLEET) Management (Onboarding & Offboarding)
SIP2.Y Strategy (ARK) Management (Onboarding & Offboarding)
SIP3.Y Token Rewards
SIP4.Y Governance Parameters
SIP5.Y Special Governance Votes (One-Off Proposals) 
⚠️ In case there are subsequent proposals to previously posted ones
(e.g.: SIPX.Y), instead of creating a new "X.Y+1" proposal ->
create a sub-proposal = SIPX.Y.Z (e.g. SIP5.5.1).

Use this formatting when creating a new topic:
image

Select appropriate category, and add tags for improved searchability.

1. Overview:

A concise summary of the SIP in 1–2 sentences. Think of it like a changelog entry for the DAO.

Tag forum username(s) if the proposal is co-written.

2. Motivation:

Why this SIP is necessary. Clearly explain the problem, strategic importance, or opportunity. Link to prior RFCs/SIPs or relevant forum discussions.

3. Specification:

This is the core logic and implementation plan. Provide detailed information about what the SIP will do, how it works, and who/what it impacts.

You can include the following:

  • Technical/Parameter Changes: e.g., yield curve, collateral ratio, caps
  • Execution Plan: If relevant, explain any required smart contract changes or interactions
  • Actors Responsible: e.g., SummerFi UI, Lazy Summer DAO, Block Analitica, multisigs
  • Timing: When should this take effect?

If you are proposing SIP1.X or SIP2.X use the following table template (adjust accordingly) and present the main information in easily accessible overview:

Parameter Value
Fleet xyz
Network xyz
New Ark xyz
Contract(s) xyz
Risk Level xyz

4. Risk Assessment:

Outline potential risks (technical, governance, economic, etc.) and how they are mitigated. Include input from Block Analitica if ready, otherwise summon them by tagging @BlockAnalitica in your post.

5. Voting:

Define what a “YES” and “NO” vote entails. If there is already a vote associated with this proposal, please attach them. Otherwise, follow up with a comment under the topic with a direct link to a Tally vote upon publishing.

2 Likes