Tokenswim Attestations

Proof

d347616c-60ef-43c3-af3c-6aa9482101e7

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
62d3831148d82b54c80ae75445f55ac1dc018e977a511c9d20356acbf465409f
Server digest
14f4cbc0b2bccff387f30fdfb6b82228022668e5f96157b42d3f18336d1e6a3b
Client windows
[168816, 168944) [225500, 225628) [399201, 399329)
Server windows
[47981, 48109) [99216, 99344) [136673, 136801)
Drawn against
933724 client bytes · 281770 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
566bbd09440ffc3a6c91b8f65067981b1deddb9545a5270ee97105c19ae120ad
Leaf index
1206 of 1219
Audit path
  1. 92c6f9a4dc3e2376d16b03b1b7354cf2f2643f9abfbe9647bda78950e75316b1
  2. 544dd9c001d49ba671e1184ba1df4f808c539c3969bed9094fcb8810d1a6924f
  3. ac15232062c9da6893edca726c1b717815837694612e66ce56e1b81e3045eb80
  4. 6b2a491e4be23750908e7a7786b3b5e5c6a24b6f5edde2b77ae4aa15658e88cf
  5. 213b271b4665b5e97bd86196d89ac2ba2c91f9812a5015bf1efecae9a7d254d5
  6. 6d38306fb414141a855b719052e3db207fdc749f00a65de1f445e49d0bc052dd
  7. c59a7b18d61351c80007ffb30ddc6f55569ab3bcc2d61b4c3f67d359f9690b22
  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.