Tokenswim Attestations

Proof

b622ac08-f65f-403a-8fcb-0d5e8a44628d

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
9718f0d783662f3d4c4de798947742865c9ad5445245bc42ac99cd8095135283
Server digest
c3b3494b33fce3c8601263d67ba6632ed1ecd36948ea3e84f80d1f791cba4cb9
Client windows
[107751, 107879) [510284, 510412) [533208, 533336)
Server windows
[79176, 79304) [169736, 169864) [234778, 234906)
Drawn against
657335 client bytes · 269482 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
3e9712cc8a00d294b13dbfa6120287741790484a08e87f9cea73ee5c435f68d6
Leaf index
1139 of 1167
Audit path
  1. d22910979f7a0f7cbfa907d4eb2ae0971c1d774ea1903b277cf9f656778c14ca
  2. de1b8d2121e2b0a0bff3a9307b900e1b400f25c5ebcb09ffcdc3d6d2804fc7ab
  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.