Reinstatement Request: Nexode

[Kev-Nexode]

This document outlines the reinstatement request for the Nexode app, detailing the pause reason, corrective measures taken, and compliance with the required lock amount.

Featured App Reinstatement Request

Summary

• Featured App name: Nexode
• Organization: Nexode
• Current stage:
  • Freshly paused, seeking reinstatement
  • Mid-appeal, disputing the basis of the pause
  • Already reinstated, lock outstanding

Briefly summarize what this PR is requesting:
This PR requests reinstatement of Featured App Nexode, paused 2026-08-11 UTC "pending further review" for a stated lack of adequate clarity as to the nature of Nexode's recent on-chain activity (Accountability Committee recommendation #1262). No excess amount, ratio, or specific rule violation was cited.

Reinstatement Request File

This PR adds a completed reinstatement request at:

reinstatement/nexode-2026-08-16.md

---

Submission Checklist

Before submitting, confirm:

• The completed reinstatement request file is included in the reinstatement/ directory
• The file follows the Featured App Reinstatement Request template
• All PartyIds are listed exactly as they appear on-chain
• Any fields that do not apply are marked N/A with a brief reason
• Supporting figures, sources, and transaction hashes are included where applicable (N/A — no excess or over-issuance was alleged)
• CIP-0116 locking status is included
• Any exception request is clearly identified in the reinstatement file, if applicable (no exception requested)

---

Reviewer Notes

The feature responsible for the activity has been switched off and its configuration corrected. The pause recommendation (#1262) did not identify any excess, ratio breach, or specific rule violation, only a lack of clarity, which this request addresses. Nexode has completed the CIP-0116 5,000,000 CC lock and is happy to provide any further clarification the committee requests.