Tokenswim Attestations

Proof

2b3f5043-0d53-4682-ba85-6ede9489fc72

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
ad2ebcd82cb3bd317b2f93255ac67fffec7d86f0ea4ba7d8863027f732211ea1
Server digest
c2d656cfe2cc2166839f951e44b8a482960c89233cc74d7e9cccc07441f35342
Client windows
[130807, 130935) [228014, 228142) [378323, 378451)
Server windows
[157940, 158068) [201561, 201689) [236062, 236190)
Drawn against
389501 client bytes · 280190 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
4b66acc90b988f0138957a05e26d5f0aa5e6ae096041d27e6da3f72524f23b10
Leaf index
1240 of 1254
Audit path
  1. 9f48ccf95b1f04f03850957437b704ff636d027e3435b3659eb3671346a155f2
  2. e51239a951ba589d32b51151e23d2086e49c18713735dc70392bd741d0693835
  3. 80b994941b5a35877b3f77db1c660a2704f05d9dbfc700437a3e1c6b365f51a0
  4. 9f68e6766ad92cb70b4f0b3478ca0a8c62a4fd4a56a609ecc38133e61e907748
  5. 43525f3f94a524696ae952ad3dcfe89a60d6d86f3575e9afc267a1006bd22c50
  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.