Tokenswim Attestations

Proof

fd346d8e-29e6-48ed-a96f-11e409004e15

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
84a3054de7cd3c883fbc415baf42fa7e8224b2e4ebe293bf0ec2912b806db7d7
Server digest
b4a53f7f855aa4aaeb9b1ada7deb16e675cb51b436c4c5539943ea61d2a596b4
Client windows
[111961, 112089) [732711, 732839) [831070, 831198)
Server windows
[12566, 12694) [35200, 35328) [268667, 268795)
Drawn against
957116 client bytes · 286519 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
98bde785149145dfff38665c42f9448971051802521ad3f97b85038d23839ed8
Leaf index
1208 of 1219
Audit path
  1. 8ec2ac266577c8b25d80b913e353956bb447c36f1a3a535d056fd229e7beb905
  2. 23970768a3ef08edfe51ed96c0bf66fda5d9feb2e80bf9e640e38205c3a3940e
  3. 56368836889bf82080b603f3a9f5761d8215f869417ba96e0e8333162ef3b6ac
  4. da9483448953dc44eb638b62447702be02426b7758d4420d671bd17ad1a8f44d
  5. 213b271b4665b5e97bd86196d89ac2ba2c91f9812a5015bf1efecae9a7d254d5
  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.