Tokenswim Attestations

Proof

4799b4b7-0910-4311-abe5-21c1e30b2a7a

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
c4bbc9a62380c07bbf1ce40003bfc104935af3fe38173999f24db7b8fe65e277
Server digest
bf5e4484c3cd95805e394f5903f4eca93ba311b5df81964fc3e19f1815f59e1f
Client windows
[111634, 111762) [154151, 154279) [257290, 257418)
Server windows
[246239, 246367) [351910, 352038) [425907, 426035)
Drawn against
428405 client bytes · 1361267 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
64af295c3c00f9264b3f681213455e101ca679546c4a241b51d674bdac9eaed8
Leaf index
1245 of 1254
Audit path
  1. a548178e6502d5d7882c1473bc3b60c2502bb52208242f94447038d4a7099948
  2. be97573e5eea890a458257c4c5bccd6f413f770d051c7858f6e3e71ebd1e0386
  3. cac77ab69df81c8f75e103263c84d58571cf600ab5e24a219ee4cadae0985335
  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.