Tokenswim Attestations

Proof

309047ea-9544-4bc6-b7e6-1a23402ea76e

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
ced5e4944f5d00d07cd35f0a9a43ae6dd83c6e8e9a5452b24ca27f82f5953a06
Claimed model
gpt-5.6-luna
Session at
Client digest
e3ff29d49d4924a76696dba27fefa56f692a7b7ebbade757770c5384fcf06751
Server digest
fcd3d66024b46a7b1140f5816dab3f9cd150fb2c1161f0f9d18102eee40b3c9b
Client windows
[90566, 90694) [142937, 143065) [185797, 185925)
Server windows
[47041, 47169) [77399, 77527) [270367, 270495)
Drawn against
200695 client bytes · 336032 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
be5a6fce98c4b1cf39f2ccab64b4b003ceb5c41ff0b523b4afffabd7dbb298db
Leaf index
1074 of 1093
Audit path
  1. 163f729155b9be7980e4d1ec8c8a538c6244e47070a35a16b04f1551262c36b7
  2. c670088a3ffd80f9c5eec1397dd3ad270e9f5b8472ad4072a7be0bae5db7c607
  3. 4ac17c5ccb62642f0a7f35bb88d5fed22c55aeda8bf366be7164a1457d2a3c76
  4. 07ce24c848b039ad6ef86c4f56c1c49a6b76c7574da1f293d6a4250a981ab003
  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.