Tokenswim Attestations

Proof

04db4859-5a0f-48e1-b1b6-a1c782b86676

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
fd2dfe1c9532772c0908a61af1d86d68ad39e6938e4679835507a01bb45f307c
Server digest
32130a6d419f1bbcc905cd3fd346cbe982aa47cf7d8f6e0b5e1242cc09eb5105
Client windows
[415740, 415868) [541067, 541195) [662532, 662660)
Server windows
[4229, 4357) [99245, 99373) [104192, 104320)
Drawn against
717949 client bytes · 309957 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
5365ad5825538d8650f8f6b0eaea7f64e8460231ffd157f0f9ebd5331321e630
Leaf index
1198 of 1219
Audit path
  1. 8fea924868ce42aa8b294cdbd682bb8f2626c0babb37062fee0bf5849b0c004d
  2. 110070c78c62d6112d3930c70f22d464ec739c57c1b0dc991f1f944a43024baf
  3. 2545811dad560b3766b52b208969ceea09a14f20dffb1e779cc358f9cb6694fb
  4. d80a94ce8940585f2c5b9bf7d5a584a70e594057e9574e002e0faf8deaecd750
  5. 1694111a394ba648935f120515d734ba49c96b071b5ad6b1f4ee98f9dc5f333e
  6. 6d38306fb414141a855b719052e3db207fdc749f00a65de1f445e49d0bc052dd
  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.