Tokenswim Attestations

Proof

ef9a8b4d-e7ba-48ba-ade8-39ca5b63cbbd

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
a5a25cdd9a8f829d3653a97a7c0f32c6a80b162cad62e06adf7c607185b25ad7
Server digest
4e43ed15fbd595eb656fbc653257ee836c7650bc6687b1749bb1ca4d0b8e1a57
Client windows
[72563, 72691) [140556, 140684) [158391, 158519)
Server windows
[3065, 3193) [183583, 183711) [244185, 244313)
Drawn against
223917 client bytes · 265479 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
cb8d5073501ec14152bf643a61ec74e3e0c74aa149a97ede60e5da417b5fd91f
Leaf index
1267 of 1270
Audit path
  1. 7f445606e5ca51a76b27e9053061c84262646b92385e9f24955073d8943a5728
  2. f2f0916e0ccef0618669c616dfe533f733f2080284964e5351af9f60c3fc4484
  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.