Tokenswim Attestations

Proof

5efbd443-fd0c-4d04-8c5b-63ef016a3609

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
ced5e4944f5d00d07cd35f0a9a43ae6dd83c6e8e9a5452b24ca27f82f5953a06
Claimed model
gpt-5.6-luna
Session at
Client digest
358cf52b151a46e9e91485b5e26e8fe61dd1f63687f6c32038225f43b1d34de6
Server digest
b64039b9baf3fe87c524d888d8286c19a89e46a05f4a5074a1d22f9e66adff24
Client windows
[64411, 64539) [131185, 131313) [147463, 147591)
Server windows
[187002, 187130) [282190, 282318) [284856, 284984)
Drawn against
255304 client bytes · 328680 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
3fdca124a9fc3cb559c1bc07bca77028dbbefadc7ce1d061d4604128113e90e7
Leaf index
1084 of 1093
Audit path
  1. 070e032c6971b37035b1d8299d8b5e2e79829c8d2b3012cd42501f859cf82a83
  2. 9f494911f5aebe271e4e1443d45262873008506c79e586b77d52cdae16ff0a30
  3. f54769a7abed583ab062c0590f810d40b2978f4c97c02cfaaa8c6590c937d19a
  4. a9aa7e33e3d93e2a5f0ba1b57a985fc4088eadba59d80f2b2135339eac0f13ad
  5. 5927259d8c35460fd2c7dd30a43c4dfe2054fedd007a1cefd69432c134ae60d2
  6. a742a5360896912df0e8eafed3427a86ac196c8845edddce95bfb74644565e47
  7. 6dee37adee250a990d348c1869165468a659ba504c4e5c8b7131596addea693a
  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.