Standardizing Proposals Structure

I suggest standardizing the proposals structure to make them more readable (and also starting to name and number them - PowerPool Improvement Proposal (PIP) could work).

I think what YFI and CRV have implemented works pretty well.

Here’s the structure YFI uses:

Summary:

Simply 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 YIP is implemented.

Motivation:

This is the problem statement. This is the why of the YIP. It should clearly explain why the current state of the protocol is inadequate.

Specification:

This is a high level overview of how the YIP will solve the problem. The overview should clearly describe how the new feature will be implemented.

For:

Against:

Poll:

6 Likes

pretty neat structure, I think we need to pin that thread

Or include this structure in the post:

Wow. Really decent.

Strongly agree.