Delivery roadmap
The specification’s build order, with honest implementation status.
MVP sequence
The PDF orders the backend foundations before the dashboard. This delivery implements the frontend preview first in response to the requested website adaptation; it does not imply the earlier backend phases are complete.
| Milestone | Scope | Current status |
|---|---|---|
| RH Chain RPC setup | Redundant RPC pipeline and raw block parsing. | Backend planned |
| Onchain reader | Read totalSupply, pause state and proxy implementation. | Backend planned |
| PoR & oracle engine | Integrate Chainlink PoR and custom attestation ingestion. | Backend planned |
| Reconciliation engine | Apply explicit rules comparing supply with verified reserves. | Backend planned |
| High-speed API | Expose full reconciliation and lightweight status endpoints. | Backend planned |
| Dashboard UI | Address lookup, proof rendering and audit view. | Frontend preview available |
| Event alerting | Webhook and Telegram/Discord notifications for desynchronization. | Planned |
Source: PDF p4 §11
Backend acceptance
These are the product definition of done, not claims made by the current frontend deployment.
- Address queries return a deterministic, evidence-backed SAFE/WARNING/BLOCK status.
- Onchain supply is reconciled against verified offchain reserves.
- Oracle staleness and permissions are actively evaluated.
- Third-party protocols can access the low-latency API.
Source: PDF p4 §12