Tokenswim Attestations

Proof

f93a0614-6778-4c7b-b488-fe28dfdb09ac

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
16b2460199922ea4b34a434896b3582d769f0d3a9aea45b3fb12eefb24ea51b1
Server digest
a46e8c0ae8ab958063e397ac5de5229f2fa87e5748b399eb5c8b3bb257aeeaed
Client windows
[86241, 86369) [235797, 235925) [301563, 301691)
Server windows
[93343, 93471) [218634, 218762) [246391, 246519)
Drawn against
358023 client bytes · 301528 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
3e615b89fff78910bb6d1e629b7f5a677b99740bba44114ec9864d668bc23850
Leaf index
1149 of 1167
Audit path
  1. 926896b69a6bcc920e466d4ee2e3a8e4659e7a142ea2209750013a88b080baf6
  2. 96b4614d93ed9230956cdcc430debaa8c818e313b086adde3baa898820d642bf
  3. 6be693ffddecbc899d476a3b4b033751aa6dcde895adb9fee173b6941c67b119
  4. 0e964c43fc4090a763b787357f96f4afd5175081337619f0c63d53159230e419
  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.