-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PLIP 1: PLIP Purpose and Guidelines #1
base: master
Are you sure you want to change the base?
Conversation
Hi, thank you for great Guideline!! |
Great question! PRC comes from ERC which stands for "Ethereum Request for Comment." So PRC would be a "Plasma Request for Comment." It's surprisingly hard to find what "ERC" stands for, but you can see it explained in the Wiki article. |
PLIPs/plip-1.md
Outdated
@@ -0,0 +1,218 @@ | |||
--- | |||
eip: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plip
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed it :) Thanks for the catch
Thank you! Now everything make sense!! |
Each PLIP should have the following parts: | ||
|
||
- Preamble - RFC 822 style headers containing metadata about the PLIP, including the PLIP number, a short descriptive title (limited to a maximum of 44 characters), and the author details. See [below](#plip-header-preamble) for details. | ||
- Simple Summary - “If you can’t explain it simply, you don’t understand it well enough.” Provide a simplified and layman-accessible explanation of the PLIP. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO add a "Terminology" section as well. A lot of jargon in our community:) A PLIP that tracks all standardized terminology might be a good idea. Most ppl have no idea what a predicate, an exit game etc. is
- Preamble - RFC 822 style headers containing metadata about the PLIP, including the PLIP number, a short descriptive title (limited to a maximum of 44 characters), and the author details. See [below](#plip-header-preamble) for details. | ||
- Simple Summary - “If you can’t explain it simply, you don’t understand it well enough.” Provide a simplified and layman-accessible explanation of the PLIP. | ||
- Abstract - a short (~200 word) description of the technical issue being addressed. | ||
- Motivation (*optional) - The motivation is critical for PLIPs that want to change the Plasma protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the PLIP solves. PLIP submissions without sufficient motivation may be rejected outright. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A proposal without motivation seems... weird? Shouldn't be optional imo.
Co-Authored-By: Georgios Konstantopoulos <[email protected]>
This PR adds a proposed PLIP 1. This PLIP is modeled after https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1.md which defines the much of the foundational structure for future PLIPs.
Figured this would be a good model considering it seems to work for Ethereum. That said, I did make some changes to their wording & so would love feedback.