420Docs context
Skip to content

VERIFY-10 — qualification, reconciliation and closeout

VERIFY-10 closes the GEN-10.5 / 420Verify implementation phase by reconciling the long-lived Verify branch with the latest main, preserving the verification trust boundary, and requalifying the exact final branch head before merge.

Closeout state

  • Service identity remains 420/service/verify/v1.
  • 420Verify remains contract-free and non-canonical.
  • Chain state/RPC remains authoritative for deployed bytecode and runtime code hash.
  • 420Registry remains authoritative for registered identity and legitimacy.
  • Verification evidence cannot grant Wallet, Smart Account, Registry or governance authority.
  • FULL_MATCH means exact reproducibility under the submitted source/compiler/settings evidence. It does not mean audited, safe, official, immutable, endorsed or non-malicious.

Implemented qualification surface

VERIFY-0 through VERIFY-9 provide the complete implementation surface required for final qualification:

  1. architecture invariants and trust boundaries;
  2. service/runtime fail-closed qualification;
  3. canonical deployment evidence acquisition;
  4. deterministic source/build commitments;
  5. pinned hermetic compiler reproduction;
  6. exact bytecode comparison and stable result classes;
  7. append-only reproducible evidence history;
  8. proxy detection, implementation separation and upgrade invalidation;
  9. public lookup/submission/evidence APIs and Genesis consumer boundaries;
  10. adversarial input, resource, compiler, corruption and authority hardening.

Reconciliation evidence

The latest main was merged into feature/gen10-5-420verify-v1 during VERIFY-10 through reconciliation PR #304. The reconciliation merge commit was afaf3e9f669590299c4b0898341f8195db30d441.

No public endpoint deployment is claimed by this document. testnet/public-services/verify/readiness.json continues to distinguish implementation qualification from actual deployed backend/frontend URLs.

Final qualification requirements

The exact final head must pass:

  • 420Docs Qualification;
  • 420 Integrated Qualification, including go test ./...;
  • offline-core;
  • production-dependencies;
  • fault-matrix;
  • geth-engine.

A final head is merge-eligible only when all required workflows are green against that exact commit. Any code or documentation change after qualification invalidates the closeout evidence and requires another exact-head qualification pass.

Phase handoff

After the final head is green, PR #303 may be merged once into main. GEN-10.5 is then closed and Genesis application work advances to GEN-10.6 / 420AppStore.