| title | date | ipip | editors | relatedIssues | order | tags | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
IPIP-0000: InterPlanetary Improvement Proposal Template |
YYYY-MM-DD |
proposal |
|
|
0 |
|
This is the suggested template for new IPIPs.
AKA Problem Statement
Clearly explain why the existing protocol specification is inadequate to address the problem that the IPIP solves.
AKA Solution Proposal
Describe the proposed solution and list all changes made to the specs repository.
The resulting specification should be detailed enough to allow competing, interoperable implementations.
When modifying an existing specification file, this section should provide a summary of changes. When adding new specification files, list all of them.
The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made.
Provide evidence of rough consensus and working code within the community, and discuss important objections or concerns raised during discussion.
How will end users benefit from this work?
Explain the upgrade considerations for existing implementations.
Explain the security implications/considerations relevant to the proposed change.
Describe alternate designs that were considered and related work.
List relevant CIDs. Describe how implementations can use them to determine specification compliance. This section can be skipped if IPIP does not deal with the way IPFS handles content-addressed data, or the modified specification file already includes this information.
Copyright and related rights waived via CC0.