Tokenswim Attestations

Proof

48154baa-4d2d-4025-af12-b6c662a8406f

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
ced5e4944f5d00d07cd35f0a9a43ae6dd83c6e8e9a5452b24ca27f82f5953a06
Claimed model
gpt-5.6-luna
Session at
Client digest
c1c420aa1c8e43e279c8e0dbc50a941e4712a28565a1df29a362a0232b6172c7
Server digest
8bff433b1a15922dc4d2262276f0e89ea1a7e2c3f2564da95375685679892c85
Client windows
[13824, 13952) [45721, 45849) [125793, 125921)
Server windows
[47169, 47297) [205407, 205535) [242172, 242300)
Drawn against
204928 client bytes · 364601 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
b7cb42f2647032591c7cbb4a0c7c3d6c20b3d9708f4b5c5656585bbc3dc17e6c
Leaf index
1076 of 1093
Audit path
  1. 9babc107ac3602628165e9196c662ae17e4174b10d1d46a63989ad34c94bf80f
  2. 70ffb52143e00780efed216a6e0d36754d8325a4256e30d947c63ccd92b843c9
  3. 27bbd9d1f3f0b2059f1c2770f6745f1951ab9b7b59ec29fe5f6ae6672f90ffc5
  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.