Tokenswim Attestations

Proof

6ed404e5-c20e-4222-bd86-9e1ec98e5a33

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
4659bc47e224ee06e3c886db9dd9f79db32839759164b06e56d2c7f7a5f1fa79
Server digest
f26b2385f9816ab62dcb5e3839e6941d5523b333756fd300efe1e5f08ccd912b
Client windows
[13223, 13351) [33890, 34018) [125545, 125673)
Server windows
[23572, 23700) [103588, 103716) [180392, 180520)
Drawn against
267718 client bytes · 256653 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
7afa22321b684f7335e7b8a803e7ec6e5afa58bc4914195d81374601a73ca424
Leaf index
1186 of 1219
Audit path
  1. d4488e26dbe14005818ac9a1c4e340ceacc305b6307b429504b6f613c386589c
  2. 3b41db83f2b5bbec5311b03f3ee55f95197ac45bb9e8f58f62ee96a4fa79dc8c
  3. 24ee8f8121f8fd9c14cc4aa2dacc83b80e461463a41d6757584e7e4098d8f5aa
  4. c3a0c88215f7b76ab77defe80952a0d92fa5c7112db45a02a5f8efad109e7232
  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.