Tokenswim Attestations

Proof

bed26b90-cc56-4f50-916b-3962fb78d2c1

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
9b430e89d413debe764cf623b6dd897bb1ff204413e591734d434c96316a2ae2
Server digest
19f0819bb804170b9d83b23fa3cdf7cd3fc17f9749f661fcb00d7d7d3a243caf
Client windows
[45717, 45845) [161721, 161849) [177840, 177968)
Server windows
[40326, 40454) [120477, 120605) [162681, 162809)
Drawn against
201594 client bytes · 297993 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
29f28b35d818087bd4fb89f7175e4413a8108fc6f5204d4e860ea4430686877d
Leaf index
1184 of 1219
Audit path
  1. 410132570ece3f7ced86199d48bb5b2021598d73c90ca51b319c72f65de6cc4b
  2. a0b69cc16c54921fac7fb662f01a61d374a3601849f6c6d544650c5df86fb26a
  3. 24ee8f8121f8fd9c14cc4aa2dacc83b80e461463a41d6757584e7e4098d8f5aa
  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.