Tokenswim Attestations

Proof

bfc3750b-31ed-4365-b36b-8a36bf9bc9ff

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
9ee7d7f480e58d5db01cb1e49a2ce0b59745b965810a89f08c98bb77a5e731c9
Server digest
46b965ef28fc4456f616d12cfe067569f4b92fa46a613da2ce557c800ec949b0
Client windows
[69686, 69814) [153677, 153805) [354642, 354770)
Server windows
[48251, 48379) [205584, 205712) [208832, 208960)
Drawn against
402425 client bytes · 299219 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
d0f72af92cb1a7ad558c88e8b14eb972ccb7a1ccdf16dc626ae491fe0b8bde90
Leaf index
1228 of 1254
Audit path
  1. c8118060e3ddf086af3e37172876a96d61b17bcdaf1ce1739d65b033a1c6a149
  2. 2ae82ed18a264077ff5fe8e1db596e8ecd9b7b26ca020be0f4410295be354769
  3. af92278378eec67a97073ecf12654d5510423211372efa182ae8b0d4745c2d42
  4. 7ad9ffba38bde7f97c35d2735d6a1aab069a51c719c1c8a45e440719625496e2
  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.