The roadmap moves from specification to implementation, real operation, independent review, and conservative activation. Timing follows completed dependencies and review findings.
The architecture and security specification are prepared. Contract implementation and signer operations are the next release phase.
Define the market-observation policy, independent validation model, signed payload, contract invariants, destination domains, consumer protections, operating model, and acceptance tests.
Build the oracle contract, canonical payload, independent validator paths, signer tooling, permissionless relay, manifests, monitoring, and adversarial test suite.
Deploy to test environments, integrate a reference consumer, and exercise source outages, signer loss, stale observations, replay attempts, malformed payloads, and anomalous prices.
Publish under production-like market conditions without authorizing meaningful financial exposure. Compare every price update with independent references and exercise monitoring and incident procedures.
Freeze the candidate, complete independent human security review, remediate accepted findings, re-run regression tests, and re-review material changes.
Launch with conservative assets and exposure limits, publish live status and policy history, and expand only as production evidence supports broader use.
Engineering, validation diversity, operations, security review, consumer safeguards, and public disclosure all contribute to production readiness. The release candidate advances only when the complete system satisfies its gate.
Contract invariants, canonical serialization, signer tooling, relayer behavior, and acceptance tests pass against the frozen candidate.
Required attestations span separately operated validation paths and preserve the required implementation and administrative independence.
Keys, funding, source health, alerts, incident roles, rotation, and recovery procedures have been exercised.
Accepted findings are resolved and the actual release candidate is re-reviewed after material changes.
Freshness, activation, bounds, caps, conservative valuation, targeted pauses, and safe degraded behavior are live in the reference consumer.
Addresses, source commit, signer configuration, policy, known limitations, review status, and release manifests are publicly verifiable.
