Tokenswim Attestations

Proof

6f58bdd6-aba1-49cd-8706-671b67b4de74

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
3096e600214ebe3102c7c62a16be200588e338dba1c99a0795f3d0f160ac434c
Server digest
76842d4428fa87763e2e47c3ad843022d7a20414241d2b42b7b1460fa40375d0
Client windows
[31061, 31189) [191580, 191708) [207459, 207587)
Server windows
[30936, 31064) [153330, 153458) [230299, 230427)
Drawn against
305917 client bytes · 272142 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
297d2cb428ef7ac1e1f503af0e2db62e0fed34b6b8e66ff8ca1c888bc51278fd
Leaf index
1225 of 1254
Audit path
  1. aab75a8ed8f094227bcda0ba439e59066089fb8ce9e62046a4c2a9794c737cfc
  2. 9b74f152ea5a9d185bdcb3c6d06b518e4eba72edd838a6a087a3e874081c0132
  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.