Tokenswim Attestations

Proof

35a05ba6-1a98-4c1f-9c14-8bb5ccaaeb6b

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
59214d0e5302dc0d1c6827c3ea984d4e6b8c20bc622603ae19d1f97989f7f68b
Server digest
c4e93d3b24411b066f78b71893a7c093e23713a136376e3cb09765ea62834b21
Client windows
[10335, 10463) [102802, 102930) [109006, 109134)
Server windows
[79632, 79760) [173276, 173404) [215100, 215228)
Drawn against
214712 client bytes · 300578 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
d4488e26dbe14005818ac9a1c4e340ceacc305b6307b429504b6f613c386589c
Leaf index
1187 of 1219
Audit path
  1. 7afa22321b684f7335e7b8a803e7ec6e5afa58bc4914195d81374601a73ca424
  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.