Finality and anchors
The application-facing commit unit is an anchor. The registered development-network profile uses independent ML-DSA-65 operator signatures, with seven of ten positions required for a cluster round certificate. That is a bounded profile statement, not proof of current liveness or a production settlement guarantee.
Current public evidence boundary
Section titled “Current public evidence boundary”The verified public RPC catalog exposes read-only chain statistics, current-round status, sync state, aggregate peer health, and runtime provenance. Those methods let a client bind observations to the registered chain identity and detect stale/degraded state. They do not constitute a public receipt-proof, checkpoint-proof, leader-certificate, data-availability-certificate, or exchange-settlement API.
An exact SDK can contain local proof helpers and an endpoint can expose raw checkpoint rows. Local transcript self-consistency or a successfully parsed row does not prove multi-validator finality. No certified public package currently connects that raw material to independently trusted signer roots, complete proof validation, and a production settlement acceptance policy.
Do not resurrect method names, response fields, or acceptance depths from historical source inventories. A disabled or unprobed method is not a public contract merely because an SDK type or older document mentions it.
Integration posture
Section titled “Integration posture”The development testnet is value-less and resettable. A prospective high-value integration must independently define and test its finality and reconciliation policy against an exact release, including failure and stale-data behavior. This site intentionally does not publish an anchor-depth recommendation, receipt schema, proof ABI, checkpoint cadence, or operator procedure.
Use the exact SDK release for typed parsing and keep its documented archive-request bounds. Do not hand-roll proof verification from historical prose.