Receipt for run 1: the Lab's permanent record of what it did
A claim whose data file was swapped after the market opened
A claim whose data file was swapped after the market opened
- Paper says
- 0.93
- Counts if
- 0.91 to 0.95
- Lab got
- no number
The data didn't match the fingerprint in the claim, so the test wouldn't be fair.
Why: hash mismatch
Check this yourself
You don't have to trust us or the . With Docker and Node installed, this retraces the claim on your own computer and compares the number:
git clone <this repository> && cd rerun && pnpm install && pnpm sandbox:build pnpm verify-claim 5
How much evidence is behind this?
Each step is a tougher test. Only the first one decides who wins the market.
- 1. !
The Lab's retrace of the code and data named in the claim
The test couldn't be run fairly, for example because the data changed. Every share pays back half.
- 2. –
Stress test: does the number depend on luck?
Fetching the extra runs…
- 3. –
Rebuilt from the description (experimental)
Fetching the AI's rebuild…
Coming next: a data-leakage check, for the same rows in training and test data, and a maths check on the statistics a paper reports. Neither has run on this claim.
Even all three steps can't prove the science is true. They show how well this result stands up to checking.
Verified
Your browser just re-checked these itself, so you don't have to trust this site.
Checking…
The write-up
The write-up isn't available right now. Its fingerprint is below.
The full record (technical)
✓ Verified on NEAR. See the contract's history
- Outcome
- INVALID
- 241c10238cc7508879569640c22b66789c0ab85246b8aada234abb043756fbc9
- Commit
- 563c58831162400e57dc0129eb2d2744fb3a1368
- Data fingerprints
- 65cb2675a54874bae05839ad7314c1742157cf1291320d522b6268b5d468a46b
- Software versions fingerprint
- None
- Runtime
- 0s, exit code 0
- Started, finished
- 11/4/2026, 8:28:55 AM, 11/4/2026, 8:29:31 AM
- Lab
- rerun-lab-43f5f2.testnet
- Lab code fingerprint
- 49fabb2e2f141c064ca032b253ce0f7e4f8054a781e5b3d64ee0d8a238372802
- AI used
- z-ai/glm-5.3-flash
- e3290c758f5f9819d5ecb7b1d4a540d0571f8156602b9688c8c7159cc6d70b01
- Signed AI replies
- e40e006c99f8490aaabe0183fa051d31
- Log fingerprint
- 69cc0f4d9573047991afede09158c3332f7d6758c2073b58dcf5bd6d31460446
- Write-up fingerprint
- 3b127c5cf9c76d82fc027ab8601ce4a745f1a41a30183fcdadb81fcbb3b37fbe
Show the end of the run log
data/trials.csv has sha256 65cb2675a54874bae05839ad7314c1742157cf1291320d522b6268b5d468a46b, spec says be35dcd48bdcc0222a5c4d5ef769adb4a58e77c1914af80d8aa457ad742f9b7d