Obyte Improvement Proposals
People wishing to submit OIPs, first should propose their idea or document to the Obyte Discord. After discussion they should create a pull request to this git repository with the proposed OIP. After copy-editing and acceptance, it will be published here.
We are fairly liberal with approving OIPs, and try not to be too involved in decision making on behalf of the community. The exception is in very rare cases of dispute resolution when a decision is contentious and cannot be agreed upon. In those cases, the conservative option will always be preferred.
Having a BBIP here does not make it a formally accepted standard until its status becomes Final or Active.
| Number | Layer | Title | Owner | Type | Status |
|---|---|---|---|---|---|
| 1 | OIP Purpose and Guidelines | Peter Miklos | Process | Active | |
| 2 | Consensus Timestamps | Tony Churyumoff | Standards Track | Active | |
| 3 | Community voting for Order Providers | Tony Churyumoff | Standards Track | Active | |
| 4 | Emergency replacement of Order Providers | Tony Churyumoff | Standards Track | Active | |
| 5 | Spam protection, part 1: protection against excessively large transactions | Tony Churyumoff | Standards Track | Active | |
| 6 | Spam protection, part 2: protection against too many transactions | Tony Churyumoff | Standards Track | Active | |
| 7 | Temporary data | Tony Churyumoff | Standards Track | Active | |
| 8 | Burn fee | Tony Churyumoff | Standards Track | Active |