PegNet Improvement Proposals (PIPs)
Introducing a Framework for Making PegNet Improvement Proposals
PIPs For The Win
Every great decentralized community has a process for proposing improvements to the software. I’ve put together a basic framework for the PegNet community and would invite you all to check it out. Here is the Google Doc so we have a place to discuss and work on refining them.
Framework For The “PegNet Improvement Proposals” (PIPs)
- PegNetd: Proposal should relate to code that can be implemented in PegNetd.
- Numbering: Proposals should be numbered when first proposed.
- Specific: Proposals should be specific enough to clearly implement in code.
- Activation: Proposals should include an activation height.
- Review: Proposals should be publicly available for review before activation.
Objectives Of The “PegNet Improvement Proposals” (PIPs)
- Utility: Proposals should increase the utility & use cases for PEG & pAssets.
- Arbitrage: Proposals should preserve PEGs function as the PegNet arbitrage token.
- Mining: Proposals should preserve the mining reward in order to secure the PegNet price oracle records.
- Accuracy: Proposals should increase oracle price record data accuracy & reliability.
- Security: Proposals should increase the security of the PegNet against attacks.
Template for PIPs
Abstract: “PIP1 A Proposal To Make PegNet Even More Awesome”
Specification: This proposal will increase the security and utility of the PegNet…
Motivation: We add the code to PegNetd and now the world is better.
Rationale: The code will be on the development branch for X days and be tested by the community.
Reference Implementation: Height of activation is ###,### on Factom Protocol.
PIPs Going Live on PegNet
The users / miners will update their code to the new version of PegNet(d) 3 days before the activation height and after the activation height the code will go live.
Presumption
Anything already described in the PegNet whitepaper or otherwise already implemented does not require a new PIP.
