https://github.com/rechain-network-solutions/oips
Welcome to the REChain Improvement Proposals (OIPs) repository! This repository is the central hub for all proposals related to improvements and enhancements for REChain Network Solutions and REChain ®️ 🪐.
https://github.com/rechain-network-solutions/oips
oip rechain rechainnetwork rechainonline
Last synced: 2 months ago
JSON representation
Welcome to the REChain Improvement Proposals (OIPs) repository! This repository is the central hub for all proposals related to improvements and enhancements for REChain Network Solutions and REChain ®️ 🪐.
- Host: GitHub
- URL: https://github.com/rechain-network-solutions/oips
- Owner: REChain-Network-Solutions
- License: bsd-3-clause
- Created: 2024-08-09T11:18:14.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-08-09T11:20:12.000Z (about 1 year ago)
- Last Synced: 2025-03-23T13:13:46.631Z (7 months ago)
- Topics: oip, rechain, rechainnetwork, rechainonline
- Homepage: https://rechain.network
- Size: 34.2 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# OIPs
Welcome to the REChain Improvement Proposals (OIPs) repository! This repository is the central hub for all proposals related to improvements and enhancements for REChain Network Solutions and REChain ®️ 🪐.
# OIPs
REChain Improvement Proposals
Individuals wishing to submit REChain Improvement Proposals (OIPs) should first discuss their idea or document on the [Katya ® 👽 AI 🧠 REChain ®️ 🪐 Blockchain Node Network](https://matrix.to/#/#chatting:matrix.katya.wtf). Following the discussion, they should create a pull request to this repository with the proposed OIP. After copy-editing and acceptance, the proposal will be published here.
We adopt a relatively liberal approach to approving OIPs and strive to minimize our involvement in decision-making on behalf of the community. In rare cases where disputes arise and consensus cannot be reached, we will favor the conservative option.
An OIP listed here is not considered a formally accepted standard until its status is marked as Final or Active.
| Number | Layer | Title | Owner | Type | Status |
|--------|-------|-------|-------|------|--------|
| [1](oip-0001.md) | | OIP Purpose and Guidelines | Dmitry Sorokin | Process | Active |
| [2](oip-0002.md) | | Consensus Timestamps | Dmitry Sorokin | Standards Track | Active |
| [3](oip-0003.md) | | Community Voting for Order Providers | Dmitry Sorokin | Standards Track | Draft |
| [4](oip-0004.md) | | Emergency Replacement of Order Providers | Dmitry Sorokin | Standards Track | Draft |
| [5](oip-0005.md) | | Spam Protection, Part 1: Protection Against Excessively Large Transactions | Dmitry Sorokin | Standards Track | Draft |
| [6](oip-0006.md) | | Spam Protection, Part 2: Protection Against Too Many Transactions | Dmitry Sorokin | Standards Track | Draft |
| [7](oip-0007.md) | | Temporary Data | Dmitry Sorokin | Standards Track | Draft |
| [8](oip-0008.md) | | Burn Fee | Dmitry Sorokin | Standards Track | Draft |
This version aligns with REChain Network Solutions and REChain ®️ 🪐, providing a clear and professional presentation of the OIP process and current proposals.