Tokenswim Attestations

Proof

f1e9900b-4b7c-45a7-9659-8231ec3d1658

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
5a257d690f5df46e25f992879b68ea7ce89de9cc3c9886e300f6ef90a21655bf
Server digest
b27c8a45d9bedd75b2aeea36a5c3abb58ce03c9d01c5ba88a2abd5ed153d4366
Client windows
[16922, 17050) [160210, 160338) [214084, 214212)
Server windows
[107134, 107262) [177473, 177601) [318848, 318976)
Drawn against
246303 client bytes · 336794 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
1511c1dad0d958db39b32bf0dd0e45c6575c41da52f15c5270961f28978bba75
Leaf index
1133 of 1167
Audit path
  1. 304f1f23e05cd4bd09245b54914417381b1b1e05c87eb073e8683d4c8c863ae9
  2. df75a3bde0ca19b3dfa8024277b53c3212503e096578fbee0646fc7bdb6b9791
  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.