Reinstatement Request: Rapid Chain

reinstatement/rapid-chain-2026-08-09.md

@@ -0,0 +1,41 @@
+# Featured App Reinstatement Request
+
+**Applicant Details**
+* **Application Name:** Rapid Chain
+* **Operator/Organization:** Rapid Blockchain Technologies Ltd.
+* **Authorized Representative:** Murat Inceer
+
+**On-chain Identifiers**
+* **Primary Validator Party ID:** `rapidchain-validator-1::12203494523f5bb02d6388ee3de4b15ee211581b6c1dadf23b71a0d2c1043d41eca5`
+* **Contract ID (Pause Reference):** `009cccdf6592eb5538dd2c910b4420ee7b47a4ba97451499e9ee53ccd0d6d8478aca12122042b6670daba1b8262045262709ba85a1bca203df24a08e2f695ceb3e76b6bd3f`
+
+**Basis of the Pause**
+Rapid Chain was paused following a Tokenomics committee vote (SV for onchain Vote: GSF). The pause was initiated because our application appeared excessively profitable due to anomalous on-chain metrics caused by an internal traffic miscalculation.
+
+**Cause of the Issue**
+The root cause was an estimation error regarding our traffic consumption and reward metrics. This miscalculation created an unintended discrepancy in how our profitability was projected on-chain, triggering the committee's automated review processes. 
+
+**Corrective Measures**
+Following the pause, we took immediate and transparent steps to resolve the misunderstanding and align with ecosystem standards:
+1. **Foundation Engagement:** We initiated open discussions with Foundation stakeholders across ecosystem forums and Slack to transparently explain the traffic miscalculation.
+2. **Expert Guidance:** We collaborated with Anthony Merriman, who understood the technical oversight and provided highly supportive and constructive application recommendations. We successfully adopted these practices.
+3. **Committee Review:** We attended a subsequent Tokenomics meeting to present our corrections and clarify the situation directly to the ecosystem.
+4. **CIP-0116 Compliance:** Just as our reinstatement review was concluding, the new CIP-0116 locking requirement came into effect. We immediately began securing the necessary 5,000,000 CC lock to meet this new standard.
+5. **Infrastructure Stability:** In parallel, we have recently resolved a prolonged validator downtime, upgraded to `v0.6.13`, and ensured our node is operating at a 100% healthy `SERVING` state.
+
+**Any Data Discrepancies**
+N/A - All historical traffic metrics have been clarified with the committee, and current on-chain balances are verified.
+
+**Basis for Continued Compliance**
+Rapid Chain is now fully aligned with the Foundation's guidelines. Our traffic metrics are correctly calibrated, our infrastructure is stable with comprehensive disaster recovery protocols, and we have fully satisfied the newly introduced CIP-0116 requirement.
+
+**Shared Participant Node Information, if applicable**
+N/A - Rapid Chain operates on dedicated validator infrastructure.
+
+**Locking Status**
+* **CIP-0116 Requirement:** 5,000,000 CC (Featured App)
+* **Status:** Segregated and available.
+* **Details:** We have partnered with **Cashen Network** to secure the 5,000,000 CC lock specifically allocated for Rapid Chain. Transaction details and on-chain verification data will be provided to the committee for final verification.
+
+**Any Asset Issuer Exception Request, if applicable**
+N/A