Tokenswim Attestations

Proof

8584d42c-ea90-4e69-a628-9d5811f76976

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
b317ca24ec75b8b3b214eed96629a1fd949bbd6dcd45c1c3f013a55ba7ca0fdd
Server digest
1b7f766096ea12638c178c450718ce3fbbeb6863d4725ee7eedfd9f5e78cdc31
Client windows
[93395, 93523) [138857, 138985) [252151, 252279)
Server windows
[46404, 46532) [70450, 70578) [174731, 174859)
Drawn against
344068 client bytes · 258757 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
33d0cfd4eba890a525d6a8318c1ceb5fe996b68ccb52ab315088770b59a718c3
Leaf index
1190 of 1219
Audit path
  1. 32fd11fbe427d2c2a45270f61af3bbe9da37435b9a62020f2b754ce6e516af55
  2. b5da70f892e3c99c0dd544658f4ca7735cc7558196de01fc3da2dd4ca0b7f83a
  3. 22069d416144b59077dd7740bd34c1d2c6702c9419a09127a9b65b94305cb6d0
  4. c3a0c88215f7b76ab77defe80952a0d92fa5c7112db45a02a5f8efad109e7232
  5. 1694111a394ba648935f120515d734ba49c96b071b5ad6b1f4ee98f9dc5f333e
  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.