Tokenswim Attestations

Proof

0682c3e7-310f-4756-b912-c3bfbc16ea84

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
460d68fa941643997bf963e37b6f4fc6eb38b9c88922a53f16c3e0495e6c6599
Server digest
fbca3f5ebc57716bbdcd26e036eec4595ce889bd98e1173c2b954120acf4428f
Client windows
[154888, 155016) [572693, 572821) [911295, 911423)
Server windows
[411655, 411783) [692098, 692226) [1106932, 1107060)
Drawn against
1091028 client bytes · 1120008 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
ea926a2ebb2042ece2e2682ccc5c27fc9a64314fc85ee472e0bd3028a576827f
Leaf index
1212 of 1219
Audit path
  1. 2e4228d121cdcd6dbcc1ef0b9c3d1239b95793cdf835514d7739f401b8ce800d
  2. d7ae153dff74a68d2f6446fa93eea81751526c8f7f2dc44ab33b9858a96b7ba0
  3. 59cc74468af994edf467a1235880dda35f5b4299a6facd0ed2adb39d77698721
  4. da9483448953dc44eb638b62447702be02426b7758d4420d671bd17ad1a8f44d
  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.