Tokenswim Attestations

Proof

2912668d-4adc-4b59-92b9-8ea2ef47e0eb

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
bb9ad70ce8ab353cbfebcb7c4431529f3c84319fd7800a2681e119221a3fa6c1
Server digest
f730b503970d78434d836ce3df697138b413ed3beedaade5a9b2cf4fcf535c45
Client windows
[206301, 206429) [260983, 261111) [273347, 273475)
Server windows
[40696, 40824) [82093, 82221) [112166, 112294)
Drawn against
280560 client bytes · 297399 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
689852b577c62d26b48acd05e2f7fdd6678639e5a8b38ef62d2dab6da98c92a9
Leaf index
1219 of 1254
Audit path
  1. ea5a2cf3f1ca65447654811988fddda2a57154033ee67e9d8bcd5f1db985354d
  2. 602ea53d10895b8fd20abdc46ca78ac11a923285f13839586ddd8226f2209ec7
  3. a6b32e0055bf4b1cab72632d3b814bd91e1512e61de023d8f6397c9c1b57ce14
  4. e30d7a54690b0bf8ae07bd5716b7baad920e7775c32258780fa1725084899b18
  5. 400ec3b8c93beda26c7f6ebb07545bc39a821b6b5335dfd87904c2e010de7203
  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.