About the PEBL RFC category

(Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters.)

Use the following paragraphs for a longer description, or to establish category guidelines or rules:

  • Why should people use this category? What is it for?

  • How exactly is this different than the other categories we already have?

  • What should topics in this category generally contain?

  • Do we need this category? Can we merge with another category, or subcategory?

Overview

This guide explains how to take part in the decision-making process for PEBL, a token similar to an ETF built on Reserve, by starting a Request For Comments (RFC).

It covers what an RFC is, how to create one, and what you need to do before and after submitting it.

What is a Request For Comments?

A Request For Comments (RFC) is the first step in the decision-making process for PEBL. It allows you to gather opinions and suggestions from the community about a proposed change to PEBL. This feedback can help improve the proposal, and then an official Improvement Proposal (IP) can be created through the Register dApp.

Constructing a Request For Comments

When you post an RFC on the governance forum, make sure to include all the details of your proposed change. This helps the community provide useful feedback and suggestions. It’s also a good idea to add a poll to your RFC to get a general sense of community agreement, which can increase the chances of your proposal being accepted.

Here’s a simple template to help you create your RFC:

Title Description
Summary Describe the outcome the proposed change intends to achieve. This should be non-technical and accessible to a casual community member.
Abstract A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what will be done if the proposed change is implemented, not why it should be done or how it will be done.
Problem statement This is the why of the RFC. It should clearly explain why the current state of ETH+ is inadequate. It is critical that you explain why the change is needed - why the proposed change is superior to the existing situation. This is not the place to describe how the RFC will address the issue!
Rationale This is where you explain the reasoning behind how you propose to solve the problem. Why did you propose to implement the change in this way, what were the considerations and trade-offs. The rationale fleshes out what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.
Risks Describe what the risks behind your proposed change are. What could go wrong after this change has been implemented? What would need to happen for that situation to occur? What are the chances of that situation occurring?
Community poll This is a reminder to add a community poll to your RFC.

How to add a poll to an RFC

1 - Click the gear icon in the toolbar and select “Build Poll”:

image

2 - Select “Single Choice” and create a “Yes” and “No” option. Press “Insert Poll” to create your poll: