Tokenswim Attestations

Proof

dfd2715a-dfb9-4782-bec8-5c6296f65bda

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
7d7487940827f10d4dd86b1784bc000784e9b19dd6d49e9cd5cbc77cc87d4924
Server digest
1f7650ae246cc863da857f7e051e6c3ec03edc3eeafbf45e6ec8eca28d330614
Client windows
[28026, 28154) [135308, 135436) [160259, 160387)
Server windows
[48471, 48599) [277313, 277441) [298874, 299002)
Drawn against
199894 client bytes · 303938 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
517100aadfc3baf08fdf5b9871f19da586a12db8cfbd5e4dc8f83786b588b2da
Leaf index
1181 of 1219
Audit path
  1. ea2697715f0f20c12850d2bb848e11555be9d1767a167026bdf2a79ca2fd8eac
  2. 480229fd8d4f159d51b14294f38415a92a2ef00ddd16f77f5aa9d02a1be13755
  3. e1556193f259d6bd5dd66cce9b002580e8e893d4a97d4de2d0d6dea51cdfdac2
  4. 48304fb1e551fe999961a84c5456a51d9586b68011f7c3621df66f340e1e73de
  5. cda182b64e12adbd40056135486c2a8855b01a8a826068381627982db69cb37f
  6. 401e5f0cdccfb000440660f404d31fe83eb5aff794647fa19212b440b0c3b150
  7. c59a7b18d61351c80007ffb30ddc6f55569ab3bcc2d61b4c3f67d359f9690b22
  8. 042dd7f38d4c4574b5c0582fdc65b11f79af6c1a9fecb526af92b88aee61bfa3
  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.