Tokenswim Attestations

Proof

702c9fd5-3fad-43db-8e01-0bd3f39d8507

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
efccef1dd7646c0d9ddcec4833d540daa9c6aee7182bb97aea1232939631985f
Server digest
0f6d0b6e6070f0a317afc5c23829b1826b8eb84d92471aaef8cd8fbeb55fa6b8
Client windows
[98502, 98630) [137132, 137260) [395109, 395237)
Server windows
[19305, 19433) [84224, 84352) [267619, 267747)
Drawn against
403973 client bytes · 276241 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
0a9003261094874e810cb539c630a702bab8ada1c4ed36eb96be9ea213cb6bad
Leaf index
1242 of 1254
Audit path
  1. d8ef0b6322f0ed46fe9e06f3263c34f971e95ac0bde8fddd62b6607f113e6396
  2. a02f2ad77067df8f0c402e5446a7e3d196b48e0737747c6095bd18edcaf942a4
  3. 80b994941b5a35877b3f77db1c660a2704f05d9dbfc700437a3e1c6b365f51a0
  4. 9f68e6766ad92cb70b4f0b3478ca0a8c62a4fd4a56a609ecc38133e61e907748
  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.