Verify
This site claims only two things you can check yourself: the journal has not been quietly altered, and every decision can be reproduced from the raw price data.
Current head hash
cbd5a96509f07bdf74fe816e3da1e7cc441f0d18e431a33ceaef1d830a92142f
- Journal entries
- 120
- Raw candles
- 730
- Last candle
- 05/10 02:00 UTC
- Recorded off-site
- Not active yet
Check in this browser
The button below downloads the journal and raw candles, recomputes every hash, then re-runs all three strategies with the same code. It all happens on your device; nothing is sent to a server.
What gets checked
- 1
Intact hash chain
Every entry is recomputed and its link to the previous entry is matched. Changing a single number breaks the chain.
- 2
Identical replay
The strategies are re-run from raw candles. The replayed journal must match the published one exactly, hash for hash.
How the hash chain works
Every simulated trade becomes one entry. Each entry stores prevHash, the hash of the previous entry, and its own hash is computed from its contents. The first entry links to 64 zeros.
hash = sha256(prevHash + canonicalJson(entry without the hash field))
Entry #1Nekton · Enter long
- prevHash
- 0000…0000
- hash
- b559839b…06f5
Entry #2Benthos · Enter short
- prevHash
- b559839b…06f5
- hash
- 67e85f8e…36a9
Entry #3Nekton · Exit
- prevHash
- 67e85f8e…36a9
- hash
- b2e56c82…2ccd
Each entry's hash reappears as the next entry's prevHash. Object keys are sorted alphabetically and written without whitespace (equivalent to RFC 8785), so anyone gets the same hash.
Run it yourself
The strategy code will be available in a public repository. Then run:
$ pnpm install $ pnpm sim:verify
The script checks the hash chain, re-runs the strategies from raw candles, then compares every entry.
Recorded off-site
A hash chain only proves the journal is consistent with itself. If the whole journal were rewritten from scratch, the chain would still look intact. That is why the latest hash needs to be recorded somewhere we cannot quietly change.
Not active yet: the public repository has not been opened. Until then, this step cannot be checked and the "not altered afterwards" claim does not yet apply.