NORTHSET
Statement-Freeze Receipt
No. 0008
Eighth settlement · task 22
A changed statement cannot pass as this one.
It was frozen at one public moment, and anyone holding this receipt can check its totals against that exact frozen list without calling us.
1 · Frozen
On 27 July 2026, this exact 30-item statement was locked at one public version. Change one item and it becomes a different statement.
2 · Proven
A public on-chain check confirmed the totals were computed from exactly that frozen list. Anyone can re-run the check from source.
3 · Shareable
Send this receipt to whoever questions the number. They verify the same statement and totals without waiting for anyone.
30
missions in the frozen statement
open-source contributions to outside projects
14
merged into outside projects
merge commits verified in repositories outside Northset
Every mission in the frozen statement, in order. Filled means merged upstream.
Why this matters to you
When a counterparty questions a payout, you send one receipt. They verify the exact statement and totals themselves, so your team does not reopen the month and your credibility is not the thing being tested.
Getting one takes almost nothing: you export one list of numbers, we produce the receipt and the verification package. Your statement process and your money flow stay exactly as they are.
Read this honestly
- The check proves the totals were computed from exactly the frozen list. The ledger behind this one is Northset's own public record, open for anyone to inspect.
- This ledger is public, so its list travels with the receipt. For private partner data, the totals are proven while the list itself stays unpublished.
- Northset operated both sides of this run to demonstrate the full lifecycle. It is our eighth settlement on Arbitrum One, and the first on the current verifier route.
For your engineer: verify it yourself in three steps
- Rebuild the list: check out commit
bfe5e0f2f6839892b02b197a61db4c0710b83323of the public ledger repo and apply the published rule, or run the published extractor. The derivation artifact lists every mission and value. - Recompute the fingerprint:
keccak256(abi.encode(uint64[] values))must equal the inputHash below. - Check the chain: the TaskCompleted event of task 22 on Arbiscan carries that inputHash and the proven totals in its publicValues.
Committed list fingerprint (inputHash)
0x846b6d89d9195fd24b982b22cd6d5f31e7f8038ad326c23f88fd2c1fdb343c1a Proven result fingerprint (outputHash)
0x017fa6dd03dcaaff55434c29cea86b2d02b3ebb7e499d8a9c30a3ab778268edb USDC moved automatically when, and only when, the check passed.
Settlement timestamp: .
Verifier contract
0x43eb16511bcaB838f9D0dbbEF85b61DD8E88602C Program key
0x00423a9fa7cb199ecc746a26a6ac7853f1df39f4be865c98c73243c39fbba645 Guest binary SHA-256
0x862e31f338990084240efabeceacc6233299ca70ee724fe236f0690866b30a5a The guest binary is reproducible from source under CI. The list fingerprint is computed directly from the values, so a short public list like this one can be reconstructed from it. Timing is established by the chain's own timestamps.