Tokenswim Attestations

Proof

bbc866bf-7982-4c91-8501-502478815258

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
34af792d5f306f7b1663c1735221e6eb1920299b269c571e0973a5fc88303c22
Server digest
2fdf1b63a69b6b253c343ffad49e4321c1d370d34167ef770743de48ec1cc51a
Client windows
[108476, 108604) [112245, 112373) [171536, 171664)
Server windows
[47410, 47538) [75468, 75596) [130317, 130445)
Drawn against
268348 client bytes · 256291 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
9b2995659af51f93ea9647dca56fc3057c6e0b4e163477b188765fa1162d0a46
Leaf index
1124 of 1167
Audit path
  1. 11de425b3896e9abf16a6fa566daa263a8f146a1b33bc0a6af0d6aa93e4f9cdf
  2. 45d198434bf8ea16f697f1cc8ba086905197cabdfb6584ea0ac24fc6bdd1260c
  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.