This repository contains the formal Rincoin Improvement Proposals (RIPs). RIPs describe consensus rules, processes, and best practices for the Rincoin protocol.
Official web interface: https://rips.rincoin.org The RIP process itself is defined in RIP-0001.
| Number | Title | Layer | Type | Status | Requires |
|---|---|---|---|---|---|
| 0001 | RIP Process and Specifications | Process | Process | Active | — |
| 0002 | Customized Halving Schedule | Consensus (HF) | Standards Track | Active | RIP-0001 |
| 0003 | Conditional Stability Valve — Scenario III Activation Protocol | Consensus (HF, conditional) | Standards Track | Draft | RIP-0001, RIP-0002 |
| 0004 | MWEB Integration with HogEx Consensus Fix | Consensus (SF, mainnet NEVER_ACTIVE) |
Standards Track | Draft | RIP-0001 |
| 0005 | Proof of Rinne — Reincarnation Consensus Mechanism | Consensus (HF) | Standards Track | Draft | RIP-0001, RIP-0002 |
| 0006 | Cryptographic Vault and ZKP Owner Recovery | Consensus (HF) | Standards Track | Draft | RIP-0001, RIP-0005 |
| 0007 | Sweeper Bounty Mechanism for Forced Extraction | Consensus (HF) | Standards Track | Draft | RIP-0001, RIP-0006 |
| 0008 | Phased Legacy Address Migration Protocol | Consensus (HF) | Standards Track | Draft | RIP-0001, RIP-0006, RIP-0007 |
| 0009 | RinHash Transaction Version Enforcement (RIN3) | Consensus (HF) | Standards Track | Draft | RIP-0002 |
| 0010 | Dynamic Subsidy Scaling | Consensus (HF) | Standards Track | Draft | RIP-0002 |
| 0011 | Taproot Non-Adoption on Mainnet | Consensus (non-adoption, mainnet NEVER_ACTIVE) |
Standards Track | Draft | RIP-0001 |
RIPs activate (or are explicitly sealed) at the following block heights (mainnet, 60 s/block):
| Block Height | Approx. Year | RIP(s) Activating | Status | Mechanism |
|---|---|---|---|---|
| 0 (genesis) | 0 | RIP-0002 | ✅ Active | Embedded in chainparams from genesis (Core v1.0.6) |
— (mainnet NEVER_ACTIVE) |
— | RIP-0004 (MWEB) | Suspended | Sealed via BIP9 NEVER_ACTIVE; reactivation requires successor RIP |
— (mainnet NEVER_ACTIVE) |
— | RIP-0011 (Taproot) | Not adopted | Sealed via BIP9 NEVER_ACTIVE; Testnet/Regtest retain ALWAYS_ACTIVE; reversible by successor RIP |
| 840 (testnet/regtest height — not 840,000) | — | RIP-0004 (MWEB) | Active on testnet/regtest | Soft-fork activation for validation purposes |
| 840,000 | ~1.6 | RIP-0002 CH activation boundary, RIP-0009 (RIN3), RIP-0010 (Dynamic Subsidy Scaling) | ⏳ Pending | Single hard-fork flag day |
| 5,250,000–6,260,000 | ~10–12 | RIP-0003 (CSV) — signaling window | ⏳ Pending | BIP9-style with objective gating, bit 1, threshold 90% |
| 6,300,000 | ~12 | RIP-0002 terminal phase entry / RIP-0003 (if activated) | ⏳ Pending | Automatic |
| 15,768,000 | ~30 | RIP-0007, RIP-0008 | ⏳ Pending | Time-deterministic hard fork |
| ~233,280,000 | >400 | RIP-0005, RIP-0006 (full activation) | ⏳ Pending | Time-deterministic hard fork at PoR |
Current chain progress: see the Rincoin Core repository.
Core development and staging take place in rincoin-core/rincoin; changes reach the canonical repository above only as reviewed pull requests. Per GOVERNANCE.md §Change Submission Discipline and Emergency Exception, the official repository is a verified record of reviewed changes rather than a direct editing surface. The staging repository carries no governance authority of its own and is not authoritative for released Core software.
Statuses are listed in the index above; each RIP's own preamble is authoritative. RIP-0002 is Active on the evidence that the schedule has been enforced from genesis on the Rincoin mainchain via Core v1.0.6, with the Phase 0→1, 1→2, and 2→3 boundaries validated in production.
Reference implementations, which RIP-0001 §RIP Status makes part of the criteria for Proposed: RIP-0002 and RIP-0004 are implemented in rincoin-sim and Rincoin Core; the RIP-0011 mainnet seal is implemented in rincoin-sim (commit 3f3aa91) and pending in Core v1.1.0; RIP-0009 and RIP-0010 are in progress in Core v1.1.0. RIP-0003 and RIP-0005 through RIP-0008 have none yet.
Note on the Block 840,000 hard fork: RIP-0002 (CH dilation), RIP-0009 (RIN3 transaction-version replay protection), and RIP-0010 (Dynamic Subsidy Scaling implementation) are co-activated as a single, well-announced hard-fork event at Block 840,000. Consolidating these consensus changes into one flag day minimizes operational disruption for node operators and mining pools. RIN3 P2P capability signaling (the PROTOCOL_VERSION bump to 70018 and the NODE_RIN3 service bit) is tracked separately as a v1.1.0 networking change and ships with that release rather than activating at a block height. No minimum-peer-version floor is imposed: RIN3 is a soft fork, and gating peers by a self-reported version would create the very split the flag day is designed to avoid.
Note on RIP-0004 (MWEB): While the specification is implemented in Core v1.0.6 and validated in rincoin-sim, the mainnet activation has been suspended via BIP9 NEVER_ACTIVE. The suspension and the decision behind it are documented in §2.1 of RIP-0004. Testnet and regtest activation at block 840 remains in effect for validation purposes. Any future reactivation requires a successor RIP per the conditions outlined in RIP-0004.
Note on RIP-0011 (Taproot): Taproot (BIPs 340–342) is not adopted on Rincoin mainnet. The mainnet DEPLOYMENT_TAPROOT is sealed via BIP9 NEVER_ACTIVE / NO_TIMEOUT; Testnet and Regtest retain ALWAYS_ACTIVE to preserve upstream test vectors and keep the codepaths exercised in CI. Unlike RIP-0004 (a time-bound suspension pending wallet migration), RIP-0011 is a non-adoption decision under the current protocol family, reversible only by a successor RIP meeting the conditions in RIP-0011 §4. The mainnet seal is applied in rincoin-sim (commit 3f3aa91) and pending in Core v1.1.0; a wallet-layer guard rejecting Taproot/future-witness sends on mainnet is implemented on the rincoin-sim v1.1.1 branch (commit 4aba34a) and planned for v1.1.1.
RIP statuses and the criteria for advancing between them are defined in RIP-0001 §RIP Status.
The Core Strategic Authority (§Core Roles), the version-numbering scheme (§Version Numbering Scheme), and the succession procedure (§Succession) are defined in GOVERNANCE.md, which is incorporated by reference into RIP-0001. Current role assignments are maintained in governance/core-role.md.
Authority over consensus-layer changes is bounded by GOVERNANCE.md §Version Authority and §Network Ratification of Release Candidates.
For security policy and Core Team verification, see SECURITY.md or visit rips.rincoin.org.
Standards Track RIPs derived from the protocol design normatively cite the Rincoin Whitepaper:
Tokino, M. On the Convergence of Regenerative Thermodynamic Security and Economic Incentives. DOI: 10.5281/zenodo.17141922
The mapping between whitepaper sections and RIPs:
| Whitepaper Section | RIP |
|---|---|
| §1 Introduction (Tetra-Lemma) | Motivation contexts in RIP-0002, RIP-0005 |
| §2 Network Specifications | (informational; not RIP'd) |
| §3 Customized Halving Mechanism | RIP-0002 (baseline), RIP-0003 (Scenario III), RIP-0009 (RIN3), RIP-0010 (Dynamic Subsidy Scaling) |
| §4 Proof of Rinne | RIP-0005 |
| §5 Algorithmic Governance of τ | RIP-0005 §6 (Delay Parameter Governance) |
| §6 Adversarial Models & Asset Lifecycle | RIP-0006, RIP-0007, RIP-0008 |
| §6.1 Type A entropic loss | (mathematical foundation; not RIP'd directly) |
| §6.2 Type B adversarial extraction | RIP-0006 (Vault as defense), RIP-0007 (Sweeper as preemption) |
| §6.3 Sweeper Gold Rush | RIP-0007 |
| §6.4 Cryptographic Vault | RIP-0006 |
| §6.4.4 Phased Migration & Temporal Smoothing | RIP-0008 |
| §6.5 Macroeconomic equilibrium analysis | (referenced from RIP-0005, RIP-0006, RIP-0007) |
| §6.7 Sensitivity Boundaries | (referenced; future Informational RIP candidate) |
RIP-0004 (MWEB) and RIP-0011 (Taproot non-adoption) are protocol-integration / Layer-1-conservatism decisions not derived from the whitepaper and are intentionally absent from this mapping.
rincoin-sim: regtest validation harness (1/1000 scale). Archived artifact (v1.0.7): Zenodorincoin-regenerative-simulations: Monte Carlo simulation suite for whitepaper §4–§6
Official RIPs are published at rips.rincoin.org. This repository is the canonical source and staging area.
Each RIP and GOVERNANCE.md carries a Canonical-URL field in its preamble. A copy whose preamble points elsewhere, or whose preamble has been altered, is not canonical regardless of where it is hosted. Verification keys and procedure for the Core Team are maintained in SECURITY.md.
Forks and other copies of this repository or of its documents carry no authority within the RIP process, and must not be presented as the official RIP repository or as a source of official RIPs. The scope of official support and liability is defined in GOVERNANCE.md §Boundary of Official Support and Liability.
Pull requests for new RIPs MUST follow the procedure in RIP-0001 §RIP Workflow. Submit Pre-RIP discussion to the #rip-drafts Discord channel before opening a PR.
All RIPs in this repository are licensed under CC0-1.0. Linked reference implementations carry their own licenses.
The CC0 dedication covers the content of these documents. Per CC0-1.0 §4(a), trademark and patent rights are not waived. Nothing in the dedication authorizes presenting a copy as official.