Tokenswim Attestations

Proof

6ed98a9e-9d2b-476a-9c83-54dfc6379522

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
8e7a0532975aab006a99d74e079351f39b2c4eefbc1de5a8e184302a34999ee9
Server digest
1b5a80f7c8ee9621b750e7e51f120f745ffcbf0a0487c3f7033a559a2ac1c11a
Client windows
[11890, 12018) [155558, 155686) [174009, 174137)
Server windows
[20146, 20274) [139772, 139900) [176946, 177074)
Drawn against
320393 client bytes · 271769 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
2ced935b15c76f5e0d6dec8f3a00fbdd67d726523362e6ef5d8f45a0c1129e33
Leaf index
1226 of 1254
Audit path
  1. d10e66a560f7d3e518ee0451cf61760e77e824abddc93cf9fc9d48ddbb963b0a
  2. e5c8bc68697d49d73cba69bdf397676380a3bcef5b0921fb055f3c8bb11cc7fa
  3. b300b2614575d27b73fa88c449a098918e4d51468fd0756fca8d000e5e51abc7
  4. 7ad9ffba38bde7f97c35d2735d6a1aab069a51c719c1c8a45e440719625496e2
  5. 400ec3b8c93beda26c7f6ebb07545bc39a821b6b5335dfd87904c2e010de7203
  6. 2bc917ad681c543c4f8c858664f8bc1f1d3f8e147ca119a9c5d5eaebcf5b1430
  7. ee15c2c6367bbe862ede633674f1c8e0ec11f544c3482e36381d215559838be9
  8. 042dd7f38d4c4574b5c0582fdc65b11f79af6c1a9fecb526af92b88aee61bfa3
  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.