Tokenswim Attestations

Proof

842fc25b-e202-4594-804e-cd0ced3e6261

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
65afb4561b2e7ece2db3bfcc282bb9a548664c2e3f69f98ad41a7d238b7db896
Server digest
c93c414fcd129028d76015cff905a917db6e1015e6031c6c7ea3df47553b60c0
Client windows
[536119, 536247) [740718, 740846) [905611, 905739)
Server windows
[59860, 59988) [81372, 81500) [211077, 211205)
Drawn against
1100988 client bytes · 284326 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
2e4228d121cdcd6dbcc1ef0b9c3d1239b95793cdf835514d7739f401b8ce800d
Leaf index
1213 of 1219
Audit path
  1. ea926a2ebb2042ece2e2682ccc5c27fc9a64314fc85ee472e0bd3028a576827f
  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.