Tokenswim Attestations

Proof

bde5e0f4-2913-4aba-995d-33925bd208c4

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-sol
Session at
Client digest
2113193cdeb03916754c5561fb32d461695eabcadc88e21f4abbab02b916052e
Server digest
26c94eb145542d7496241a5b4ab8d4d2d7f84d04aac8b2f9b40a96e18e055b7a
Client windows
[106835, 106963) [122000, 122128) [175281, 175409)
Server windows
[168, 296) [984, 1112) [1152, 1280)
Drawn against
193541 client bytes · 1667 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
9ecb52cbf6a98aca225753b04cc094f7a15de9c9a38788cb69339a51ba69cb70
Leaf index
1173 of 1219
Audit path
  1. 478246b5e6944bb0f5e1e1de9175c837077991a9251821df46082dfe7951e63c
  2. 939b4514cec0f38e3e40dd6180cc3ab0564138546f5aedc9ac1407f05c2a1db2
  3. 057783fd3de8ab3f31a3648b9828578a5e6af03c1439bfd7bdc54f7450541d76
  4. f4dd40c5f48efbe25edd915f3c41c39ad7332e10e71b019d426a9c5692ef9046
  5. cda182b64e12adbd40056135486c2a8855b01a8a826068381627982db69cb37f
  6. 401e5f0cdccfb000440660f404d31fe83eb5aff794647fa19212b440b0c3b150
  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.