Summary
This post introduces two standardized formats for Frax Governance proposals: TEMP-CHECK and FIP (Frax Improvement Proposal). The purpose of this structure is to streamline decision-making, improve clarity, and ensure a consistent quality bar across all proposals.
- TEMP-CHECK proposals are exploratory and community-driven, designed to surface ideas and collect initial feedback. They are suitable for informal suggestions, early-stage concepts, or gauging sentiment before a formal commitment.
- FIP proposals are formal governance actions ready for implementation. These proposals should follow a detailed format including technical, operational, and financial specifics necessary for execution.
Both TEMP-CHECK and FIP proposals can be submitted to Snapshot for voting and community consensus. This two-tier structure allows the Frax community to engage with proposals at different stages while maintaining governance efficiency and transparency.
Proposal authors are encouraged to follow these formats when posting to the forum.
Templates
[TEMP-CHECK] Format
Use this when you’re sharing an idea to gauge early support or initiate discussion. TEMP-CHECK proposals are not final implementations but help inform whether the idea should proceed to a formal FIP.
Title:
[TEMP-CHECK] Descriptive Title
Authors:
Your name or handle (forum/Discord name if applicable)
Summary:
A short summary (2–3 sentences) explaining what this proposal does and why it matters. Keep it understandable to someone not familiar with the context.
Background & Motivation:
Brief explanation of:
- What problem or opportunity this addresses
- Why this change is needed now
(1–3 short paragraphs or bullet points)
Proposal Details:
Describe the idea in simple terms, such as:
- What will be done
- General structure (no need to specify exact parameters)
- Which assets/contracts may be involved
- Any high-level implementation notes
Vote Options:
- For: Move forward with the proposed direction
- Against: Do nothing
[FIP] Format
Use this format for proposals ready for formal approval and implementation by the Frax DAO.
Title:
[FIP-XXX] Descriptive Title
Authors:
Your name or handle (forum/Discord name if applicable)
Summary:
A short summary (2–3 sentences) explaining what this proposal does and why it matters. Keep it understandable to someone not familiar with the context.
Background & Motivation:
Brief explanation of:
- What problem or opportunity this addresses
- Why this change is needed now
(1–3 short paragraphs or bullet points)
Proposal Details:
Lay out the implementation clearly:
- What will be done
- Any specific parameters (e.g., % fees, token caps)
- Which contracts/pools/tokens are involved
- Any technical or operational considerations
Vote Options:
- For: Implement the proposal as described
- Against: Do nothing