1/ Please join the conversations for the newly proposed DigiByte Improvement Proposal (DIP) on GitHub and Gitter. The DIP is a formal standard for proposing any changes to the #DigiByte protocol modeled after Bitcoin's BIP process.
2/ Introducing a framework for development improvements and enhancements for DigiByte will foster a collaborative environment critical for reaching consensus on critical changes to its core protocol.
3/ Anyone can submit a proposal. Once a proposal has been fine-tuned, it can be assigned a DIP number and published to the DigiByte GitHub DIPs repository. At this point, the DIP is official, but it is not yet approved or implemented.
4/ Here, it can be discussed by both the developers and broader community and can be modified and improved. If legitimate arguments are raised by a significant portion of users, the DIP can also be withdrawn or rejected.
5/ If the DIP necessitates code changes to DigiByte Core, developers may work on coding, testing, and an integration path. If the DIP achieves rough consensus, and no legitimate drawbacks of the proposal are found, then an activation path can be discussed and determined.
6/ So please join Gitter and be part of the discussions on how DigiByte can improve and implement the DigiByte Improvement Proposals (DIPs).
• • •
Missing some Tweet in this thread? You can try to
force a refresh