Review Closure Ledger
Status: current alpha closure notes after narrowing the shipped native surface.
This ledger records the current disposition of previously identified review themes. It intentionally tracks the package surface that remains shipped: exact and batch-settlement.
| Finding theme | Status | Closure evidence |
|---|---|---|
| Public surface must only advertise implemented native profiles | Fixed for current alpha | Schemas, package types, examples, specs, vectors, and runtime offer selection accept only exact and batch-settlement. |
| Batch covenant authority must be reproducible | Fixed for testnet alpha; mainnet audit still required | Escrow fixture checks, batch claim/refund transaction-v1 vectors, and covenant package tests cover the current template. |
| Transaction-v1 vectors must not be self-referential | Fixed for current vectors | npm run validate:tx-v1-consensus cross-checks batch claim/refund artifacts against the configured Kaspa consensus checkout. |
| Exact replay and batch idempotency must prevent duplicate protected execution | Fixed for current direct-mode tests | Server and client tests cover exact replay, batch corrective state, same-id conflicts, and concurrent retries. |
| Exact evidence must match x402 and Kaspa-native transaction reality | Fixed in alpha.8 source and TN10 live proof | kaspa-exact-v2 makes ordinary standard-native transfer the default and retains optional corrected additive heads. The 2026-07-15 TN10 run proved tiny and normal native payments, exact additive successor-delta economics with no second merchant output, replay/idempotency, conflict/retry, recovery, and trusted external reconciliation. |
| Hosted exact must not advertise before Worker settlement exists | Fixed and paid-canary-proven for alpha.8 | Worker version d9bac848-bc14-4326-9945-7a5a5722d63a advertises standard-native without inventory and gates optional additive on durable head availability. The 2026-07-15 hosted canary settled 198191204a1b1cc5ab79e56d83621f8cf880358ef970adf545379e0b9e3584f9, confirmed idempotent replay, and rejected cross-resource reuse. |
| Live proof harness must be reproducible from committed code | Fixed for alpha.8 source | scripts/live-adapter-reference.mjs contains the reviewable TN10 RPC, funding, both exact profiles, head conflict/reconciliation, recovery, batch claim/replay/refund, and accounting wiring. Operator-specific endpoints, wallet material, SDK paths, generated keys, reports, and recovery files remain ignored. The complete 2026-07-15 evidence is recorded in docs/live-testnet-report.md. |
| HTTP and MCP transports must not release protected results before settlement succeeds | Fixed for current direct-mode tests | Server tests cover handler failure, failed persistence, and protected-content withholding on settlement failure. |
| Facilitator support must not widen server capability | Fixed for current facilitator tests | Facilitator tests assert supported-kind intersection and explicit claim/refund settler requirements. |
| Mainnet readiness must not be implied by testnet success | Open gate | Mainnet remains blocked by docs/mainnet-readiness.md; kaspa:mainnet is a reserved profile name only. |
Remaining Gates
- independent audit of exact, batch covenant, state-store, and adapter behavior;
- production durable store implementation and operational recovery playbooks;
- fresh live
kaspa:testnet-10evidence after each release-candidate change; - hosted gateway redeploy and paid TN10 canary evidence after each hosted exact Worker change;
- upstream/community discussion before any stable registry or mainnet claims.
Source: /docs/review-closure-ledger.md