About the RFC section

2. RFC - Request for Comment
1

About the RFC Section

The RFC (Request for Comment) Section is where ideas take a structured form, allowing for detailed community feedback and refinement. This is the critical step between initial brainstorming and the creation of a formal proposal.

Purpose:

  • Provide a clear format for evaluating and improving ideas.
  • Ensure community involvement in shaping potential improvements.
  • Create a pathway for transitioning ideas into actionable proposals.

Key Features:

  • Structured Templates: Use the RFC template below to clearly communicate your proposal.
  • Community Feedback: Engage in detailed discussions to address technical, strategic, and governance concerns.
  • Moderator Oversight: RFCs require approval from moderators or core contributors to maintain quality and relevance.

Steps for Posting an RFC:

  1. Refine Your Idea: Ensure the concept has been discussed in the Ideas Section or on Discord.
  2. Follow the Template: Include all required details using the provided RFC template.
  3. Engage Actively: Respond to community questions and update the RFC as needed.

RFC Template:

  • Name: A clear, concise title.
  • Summary/Scope: Briefly describe the proposal’s aim and action.
  • Link to previous [DAO Discussion]: Attach relevant discussions.
  • Reference: Provide documentation, source code, audits, and relevant data.
  • Main Objective: Include the motivation, benefits, and solutions.
  • Contracts/Technical Requirements: List relevant contract addresses and chain details.
  • Timeline: Specify deadlines for actions or phases.

Once the RFC achieves broad consensus, it can evolve into a HeyAnon Improvement Proposal (HIP) for voting and implementation.

2 Likes