Evidence / dated development record
Technical evidence
This page separates local implementation evidence from public DEVNET evidence. It records what ran, where it ran, and what remains unproven.
Evidence snapshot: 2026-10-08
The following checks support local candidate behavior only unless explicitly labelled otherwise.
| Evidence | Environment | What it demonstrates | What it does not demonstrate |
|---|---|---|---|
| Backend test suite: 137 passed | Local Python environment and isolated fixtures | Gateway, lifecycle storage, guards, publisher, and settlement-observer code paths executed. | A funded public DEVNET lifecycle or canonical deployed-program compatibility. |
| SDK test suite: 289 passed | Local SDK environment with hermetic HTTP/RPC fixtures | Client verification, budgets, retry behavior, and instruction construction under fixtures. | That the deployed binary accepts the SDK instruction layout. |
| Candidate SBF validator checks: 15 | Isolated localnet, Anchor 0.30.1 / Agave 2.0.21 | The current candidate program executed tested lifecycle instructions and negative cases. | Any transaction or payout on DEVNET. |
| Web checks and browser accessibility evidence | Built local web artifact | Route rendering, browser behavior, and audited local accessibility checks for the tested pages. | Gateway availability, payment success, or chain settlement. |
What to verify independently
A judge or developer can verify different claims at different layers.
- Compare the configured program ID, cluster genesis, deployed account layout, source, and IDL before enabling funds.
- For funding, inspect a confirmed DEVNET transaction and its exact escrow, consumer, node, amount, and instruction binding.
- For settlement, inspect the program-scoped settlement instruction and event, then check the intended recipient balance movement.
- For a receipt, verify the signature against a trusted receipt key and compare every expected binding field.
- For content, compare the returned bytes with the committed content hash; still treat the text as untrusted data.
Current release gate
The live demo reports the gateway’s actual payment capabilities and retains recorded real funding and timeout-refund evidence.
The fresh BqM4pbj deployment uses known private owner custody and a separate dedicated settler. All 246 node commitments and 438 indexed chunks were preserved and registered under the new program. Its IDL, SDK defaults and gateway config identify the same deployed contract.
A real devnet run funded an escrow, released hash-checked content and completed a verified publisher settlement. The project demo consumer is also the publisher; exact rent-plus-payout balance accounting discloses that alias. Recorded historical refunds are not relabeled as new settlements.
THE JUDGE PATH / FOLLOW THE CONTEXT
From the idea to the evidence.
The demo uses real devnet transactions. Content integrity and a receipt signature do not establish payout. Live availability and blocked steps are shown explicitly.