Tokenswim Attestations

Proof

f21ad399-c374-48f2-a020-f6d2ba85cc12

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-sol
Session at
Client digest
36a7dfec7edd0525e24b3c42072be030cc99cd0ad876f1c7ef9975b2d49116da
Server digest
0fb2b43161e8fee80a5d0f3733b71a9895507f27c63bf55b2fb3c1be416478c0
Client windows
[41305, 41433) [89200, 89328) [138369, 138497)
Server windows
[154, 282) [705, 833) [1225, 1353)
Drawn against
199384 client bytes · 1707 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
80780c710dd04da18372e4f4a74c65d4cc27e18a53dde0e215cc814d67fa2a7d
Leaf index
1168 of 1219
Audit path
  1. 4356dbb4678750df8cec62bb1c3560ea4c35a78da0fe40b4f5c9d694eb3ae54f
  2. f2759f33eb337b73b316ba2cbf3120c2b57ae76cd114ea602d053a223bd55af3
  3. 0d2af9e8b3e5dd82b5511e9a59a9322cdabdbf0f440ef06ef78a725a562b8606
  4. f4dd40c5f48efbe25edd915f3c41c39ad7332e10e71b019d426a9c5692ef9046
  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.