Tokenswim Attestations

Proof

3a00ed3e-0540-4fc3-a683-8365db88369e

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
916c2f50dc4829363470acae9d71628a721a70ff97cbb5b42239fa7b37b9575f
Server digest
26cae4a5ebb32056fce637bd2d902f08b82464cba5b7d0527c4000dc64707e51
Client windows
[50767, 50895) [100092, 100220) [254984, 255112)
Server windows
[142139, 142267) [156150, 156278) [165300, 165428)
Drawn against
281263 client bytes · 263120 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
8af46958020952f85ae35d48d9df804f94a86842dcc240cd5bf3d71f2948b77c
Leaf index
1127 of 1167
Audit path
  1. d9a0f70b154370de85fa6dd6d30a8e80596ed060befbcce62e043b50e20101e8
  2. a367d5b33d999dfb254b8427ba543ac80e836e650bf098ce4b765a5fa5fa3e2e
  3. 36da5b3599d2cef9da6d9a41d2fb355aec96f228cc6d2af8a04d7ac51f2562d8
  4. 5b7131e72e6897444f28b6f1425f7911730c89f1df9a29078b4c8aa264625627
  5. 71a924f6204ee8a64dada0e69450128bc6b8e32e52d067786b907ec1dda57a35
  6. fb01c47cdbe5f9ea0ca22549a1957ff67e03efa700f2402342712ff35e494ce9
  7. 5a4c1362cef8e374417ac32395839f050cd870960d596a7d9c54db79870964e9
  8. 269dbab57fad6701b1f125c17e9f2d49bfba8f122e662c46aec7fae9d0efce41
  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.