Tokenswim Attestations

Proof

81d84f07-42f2-4854-be54-7aa7909b7591

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
dfd4805e4c45ce4eca956069bb3bdba43f7de07642455bdf10f67ff4a2854e58
Server digest
92c58938acd086498b6b6feb3c8d8ee0982e8f53e9f9d20c51b5314b89cc2e58
Client windows
[239974, 240102) [295249, 295377) [553042, 553170)
Server windows
[33930, 34058) [42360, 42488) [105048, 105176)
Drawn against
626050 client bytes · 297284 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
77cc93a4f611510a705fa57dfac6a1882308b558422407a69cc1b896fa5ad2e6
Leaf index
1134 of 1167
Audit path
  1. 044e8ed86a2e733be69c8d9d324fdbbda316edbe93058f2a7edd72c499363d1b
  2. 66d28a84d1316ff887b43fec5fabe98b4b81f67bd44d55f543599456b20ca2d6
  3. 6dcf28ac8eb7b57d8d01a33e2eab00a80a9440d661930358b3a4bd5e556a7809
  4. 8d18099baca8ab89bba0ef44d13739530d17b5a87c39e163f929f58546a6af75
  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.