Tokenswim Attestations

Proof

56ec33e4-4b54-4a21-905d-5394a23a8ed5

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
b0b285e8ab50cdb77506a277985fcf3f2d6b2c7e7f6ebf8feec6fba3085cd3f8
Server digest
c88d0018455561ebab5cd1e7639e68ead2628c98a942bd32f626c1e0d669a4e4
Client windows
[80111, 80239) [291456, 291584) [469441, 469569)
Server windows
[101006, 101134) [148226, 148354) [156036, 156164)
Drawn against
645154 client bytes · 279687 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
464bbe3cdae41ad487dfb73190dd1365172ea326eeda35b42c681a6f61c988b2
Leaf index
1137 of 1167
Audit path
  1. 396dbef682675570366982fd702107b50883957c9b6c5c13425bea6482b7c603
  2. 20742140941b51a54639c84c57c34e90c139ad158494fa2729c9ef406ec46a95
  3. 633718e2e5bc5cf0bc4e9736d06140d3df0f6833c36226afc6375e06a92d7b2e
  4. 5ccc89105931278b8efd01255e26c7bfc6b1599f60eb545057569dc136612627
  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.