Tokenswim Attestations

Proof

1874a7ba-3bba-492b-ae02-02e07d76673f

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
c47c8d82d84b90194dafff2ba9ab68b0c21e3b8a0d5b004200115cdccfc4042f
Server digest
c9413e2b3ddf42387b984d04ee104c4d952b6fd5a32a408a090a85ced9759322
Client windows
[72983, 73111) [1210870, 1210998) [1230357, 1230485)
Server windows
[84891, 85019) [254037, 254165) [270175, 270303)
Drawn against
1254512 client bytes · 283811 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
6dd3224f8037eb69a2cb153af14559836c17101f7bd56181082ee055bbbc9277
Leaf index
1144 of 1167
Audit path
  1. 86047a322125964e1329437611839e4dccaaf39c8020eaf263bcbf068b1a7c19
  2. c306a155513a81ac5717d99cda4f76076a7d1b8ce79b50b5617d1addb816e0b8
  3. 43cdf2ff3b7e61eea7de7d3c3db6ca7dc7f715677015ebba0b28cbbbcf2e8e7e
  4. 0e964c43fc4090a763b787357f96f4afd5175081337619f0c63d53159230e419
  5. 14fe09f1307d9f30d9b6cb0aa8ae62ea3c3a71cfe0420c52bd41e8b7a7a157d9
  6. fb01c47cdbe5f9ea0ca22549a1957ff67e03efa700f2402342712ff35e494ce9
  7. 5a4c1362cef8e374417ac32395839f050cd870960d596a7d9c54db79870964e9
  8. 269dbab57fad6701b1f125c17e9f2d49bfba8f122e662c46aec7fae9d0efce41
  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.