Tokenswim Attestations

Proof

5e7ead4a-d705-4a1e-86dd-bb3c867d345c

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
4fe67f8dfde78d6cd8e5f86891e7783c06c1a573f7942eaaebaa74a3dfa2a5ba
Server digest
b2cea8fbf88301cc506c51711de4b74e1c3249eff3ad4b7a607127ab2c05bdaf
Client windows
[190428, 190556) [280674, 280802) [355822, 355950)
Server windows
[13182, 13310) [42388, 42516) [90753, 90881)
Drawn against
369442 client bytes · 275207 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
8beab8e4ea37f44117499a8923fc7b05f5ff502eb42530d48b273b3c840bf358
Leaf index
1238 of 1254
Audit path
  1. 88d3f799f9339a1d431993e7852856f4d869ee29a0c29804a5d5021d31c549e1
  2. eb56847301c1519a14c8fcdb27007bf2f8cf9a805a87934b59237ab9696c33fb
  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.