Tokenswim Attestations

Proof

9e9813c6-bd00-4a54-b6fc-28b02edc29b1

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
6aa642998081fb4188f29826452a84ccb8e476e78e739cdc161f44e17e6de114
Server digest
1eb366715f369f51ffbea103cce56a9d6375c2b26ff79763f5cc734256259711
Client windows
[45368, 45496) [706309, 706437) [833580, 833708)
Server windows
[74197, 74325) [141538, 141666) [159517, 159645)
Drawn against
887166 client bytes · 274358 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
d33a66a3784204513e5e7c1f21b16c4fffcaa50947298367b364b7491f11ffc0
Leaf index
1141 of 1167
Audit path
  1. eaccc6d33c9186b17a4e2ee597d0db5753dc7bd790b291cfbf989bebf90be08c
  2. 6a5405a09e1fd90086ee116bbee41f19ebc82aac30650792144a3afaadce18b3
  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.