Tokenswim Attestations

Proof

e75b49e2-3a6a-4a9c-b5f5-477117ccb29d

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
85a5cc214a78cf21ed37c76766a111a3b86c5c04432b805b5ed9f4b1a6ae9b3e
Server digest
6f15f8725e012920270f3a3ff157dc3c8f8c23581db4c7290e7c74a795fb53e3
Client windows
[84768, 84896) [271083, 271211) [747356, 747484)
Server windows
[145703, 145831) [176060, 176188) [209570, 209698)
Drawn against
943716 client bytes · 276444 server bytes · 3 windows
Attestor
0x7bd8478c485a97414c430bd788d10b88d692cf2c
Circuit
aes-128-ctr+r1cs.b1338730e23d+pk.ba9bfddfb226 (aes-128-ctr)
Attestor version
attestor-core@55d43e1+reclaim-tls@e7ea68d

Witnesses (3)

Merkle inclusion

Verify this proof's inclusion in the checkpoint.

Leaf hash
b913e60e1217f7e25039ee10e2bae48640c4f52e31e3cc677ca37827225f7913
Leaf index
1142 of 1167
Audit path
  1. bbadb2c500f47820918b86cccd9cfc8c765c60aac1847a399dbe169073f52973
  2. 8a07cbb4c13cfd5ddeb5cd81afcf206e8f53a935c546ad34fd701253f60e2573
  3. 3bca0c31a94d19c41cbad473c06418796989eded9b8a54c3449dcd137e488482
  4. 5ccc89105931278b8efd01255e26c7bfc6b1599f60eb545057569dc136612627
  5. 14fe09f1307d9f30d9b6cb0aa8ae62ea3c3a71cfe0420c52bd41e8b7a7a157d9
  6. fb01c47cdbe5f9ea0ca22549a1957ff67e03efa700f2402342712ff35e494ce9
  7. 5a4c1362cef8e374417ac32395839f050cd870960d596a7d9c54db79870964e9
  8. 269dbab57fad6701b1f125c17e9f2d49bfba8f122e662c46aec7fae9d0efce41
  9. e611d69755c63040bed5a06d1a13a45121b71d7b1a4e373e89a7f71703933240

Check it yourself

Use tokenswim-verify to check the downloaded proof.

Verify the proof
tokenswim-verify verify proof.json
And its place in the tree
tokenswim-verify checkpoint verify checkpoint.json --proof proof.json

proof.json is exported by the consumer who made this request, from this page while signed in. checkpoint.json comes from the public checkpoint repository.

Verification scope

Verification checks witness signatures, challenged offsets, chunk proofs and the model reported in the proven bytes.

Matching those bytes to the full session transcript is checked by the attestor, rather than the standalone verifier.