Tokenswim Attestations

Proof

d568c45d-cada-4b39-b45b-1cc5f770276d

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
17eec56efe05c25933536a5d90b048af4fa3637e9e17896b57e3077d1fd5d615
Server digest
c36c4453ec5d61da99d10caf4a4c7bff38a2adba9ebff4e8d09db2b787ecde7d
Client windows
[34757, 34885) [138118, 138246) [175512, 175640)
Server windows
[86914, 87042) [103495, 103623) [112959, 113087)
Drawn against
203382 client bytes · 291073 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
7ea89882848ebee02cf4a9e28a6e4da2493796a5288d8a11bb19b070a64be8f1
Leaf index
1120 of 1167
Audit path
  1. 2a883583b5a2a1fdfd88e9dd86b0d21145ceba45452354aa7e8b47cd22aa2aa8
  2. 4c3be18c87b4b254e0d881d1a2761499a8b7819a9a800c1de82dba063650e08d
  3. 1e2c367dceaf1d2e655344c8f97419857bc34907d2aa5e0c18e5ffdaf56ba991
  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.