Tokenswim Attestations

Proof

3c52d704-43fe-4f8b-89c7-1b1f5c356370

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
2dad062428567c1c399e06496fef423c8ba7b8f380638a30aef87a5c2f58dba6
Server digest
cc22ea85bb1f9ab3eb6b5f059964b7baca162b8f4ca162c347f478f3c5c0a1b5
Client windows
[150152, 150280) [151121, 151249) [247310, 247438)
Server windows
[129825, 129953) [239778, 239906) [246987, 247115)
Drawn against
359226 client bytes · 332717 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
f564cefb5dd4ab900b9490f7697fd5ceb2c872a52033727a62642bb81b722531
Leaf index
1236 of 1254
Audit path
  1. 5ab5e3f199508bcf83c860b24903413df7f82ad05b4db3dc476a911c663fe608
  2. 82e01850cd7aca37cc557c852f2a4a4b800ecb7b4a0726397dcb563334c87096
  3. 1ebd716e510df37afe437b9c3e5f6be44029b5b55625c7a47020d527c8f73422
  4. 976077627aaf0b69e62d0b49cb4755d31e4dd787aded7d44fc2596ad1ce78246
  5. 43525f3f94a524696ae952ad3dcfe89a60d6d86f3575e9afc267a1006bd22c50
  6. 2bc917ad681c543c4f8c858664f8bc1f1d3f8e147ca119a9c5d5eaebcf5b1430
  7. ee15c2c6367bbe862ede633674f1c8e0ec11f544c3482e36381d215559838be9
  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.