Tokenswim Attestations

Proof

57b4240e-efd4-4754-939a-e4095bbf8b7a

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
e1400dd95bd9da4bf3268a1e205c4972850a5b361944794860719c543bab56f0
Server digest
28b235524c3888db20fbde169ead18b022001ef713772e439e5d1f2d8159162d
Client windows
[446799, 446927) [460473, 460601) [560911, 561039)
Server windows
[6296, 6424) [284643, 284771) [291548, 291676)
Drawn against
1079061 client bytes · 307711 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
f56d57592853d87c77fe702f7073b223c14cc9b55f02d345af11bb0857aac0d9
Leaf index
1211 of 1219
Audit path
  1. 629775801c6428aeeb6557131b54fe007dd73d3bfbc1fb37c076b50ba08bf266
  2. 67046a18e5dbd8309e3f8a78d3335ac6bb561f797851c91ba6725027acbad01a
  3. 56368836889bf82080b603f3a9f5761d8215f869417ba96e0e8333162ef3b6ac
  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.