Tokenswim Attestations

Proof

e3c02beb-a592-49b4-869e-ef12aa14edd3

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
ced5e4944f5d00d07cd35f0a9a43ae6dd83c6e8e9a5452b24ca27f82f5953a06
Claimed model
gpt-5.6-luna
Session at
Client digest
e40a9c1315c748af4b6b52b129bbd5623d98dceedd518b54c88838305bc80b65
Server digest
73beebb820c975dde9bbfa91d6856e39d14be5bd84f5cdd3c33d146ad29251a8
Client windows
[184718, 184846) [184888, 185016) [248820, 248948)
Server windows
[27274, 27402) [68209, 68337) [70485, 70613)
Drawn against
308964 client bytes · 316628 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
e7d8f6c55fbc6801774f564fcc1187d5c328118ba35ffc25c65f64f43bba81c1
Leaf index
1086 of 1093
Audit path
  1. 3ca451bf12e49bfcaae859c10f85e5fddc9250c0552bbeeab4a81af634b61484
  2. 4c89caf59299b596552fc1fff3c2a8b962d000ebda44a4effcbea8fad7c98c10
  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.