Tokenswim Attestations

Proof

ebf5f125-b43b-471d-9071-b80fff47d54b

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
07c0a89e298261fe728c997e3d1393d90ed9032e12eb6da7011387a1186787f5
Server digest
ae320f34e013ca7e61538c01c2e71ce54dbeac54e33a8ca4ff8a52ddec77c8b7
Client windows
[77106, 77234) [121087, 121215) [168705, 168833)
Server windows
[9966, 10094) [107181, 107309) [120959, 121087)
Drawn against
175016 client bytes · 329916 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
d50d9b4356f9cf64f226931709593700f5272f504b3b1a647ea222573e3e2cc1
Leaf index
1265 of 1270
Audit path
  1. 2c8a5c4a7f8c99ba1e1776f6e49525c4ba20a1937b256c21075f7f1b373a977d
  2. 36282e6181e159d62597367c0e09b07beca1e3615d5e62176164c605ad47d8bd
  3. 88c93cac9bc1e84fb7fe15f9b4fd3df6e8cd889148feaf69375d86f7f32ca35c
  4. 3d52e02a202d8b2dec61b292032df0af6ce933e9ee787a96e6838a94b3544fd8
  5. 3f1b7307e26cb2d3b68fa0129c9384afcb1b676161162558cf579748d4967e33
  6. ee15c2c6367bbe862ede633674f1c8e0ec11f544c3482e36381d215559838be9
  7. 042dd7f38d4c4574b5c0582fdc65b11f79af6c1a9fecb526af92b88aee61bfa3
  8. 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.