Tokenswim Attestations

Proof

18b4e6e2-6c87-4877-a179-5558b1dae1b2

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
975955f483b433501d29b5e4677c1c140b652bf9b6e00187d8278f2d0131ea40
Server digest
7c1abd8ab18455f84c360e653a7d75e953d91b47f3df85efc24440ddea58ebcf
Client windows
[541507, 541635) [612610, 612738) [809193, 809321)
Server windows
[37665, 37793) [93497, 93625) [205452, 205580)
Drawn against
1007663 client bytes · 341725 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
8ec2ac266577c8b25d80b913e353956bb447c36f1a3a535d056fd229e7beb905
Leaf index
1209 of 1219
Audit path
  1. 98bde785149145dfff38665c42f9448971051802521ad3f97b85038d23839ed8
  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.