Tokenswim Attestations

Proof

2eaf7043-549c-48bd-88ba-a553953ff417

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
50844d8c1650952a4ff1932d8ebf47e99cd175d7bccb96c67c6c3ab2212abfe1
Server digest
5436b88a73e70257d2481293cacfe55f27c0a25c84c1cfc665791890faaf8d91
Client windows
[33699, 33827) [202356, 202484) [294958, 295086)
Server windows
[27287, 27415) [35844, 35972) [184220, 184348)
Drawn against
842162 client bytes · 275635 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
0f779cb459dab40c74c57c9258471ef80b24cfe704a663b53de227e51f61f90f
Leaf index
1202 of 1219
Audit path
  1. 26ece528b4e32ca9b9d536fbe336c417b505008231dc6dfea16bcd5328f30317
  2. 714de5e93d41651753ed83ddaf9de783b23f5bd3908ae0b73a67cc3527edfa13
  3. b612411ad5d6db57d1a8b6cbd0ee4503c1d3a1a4f6fdcd45ba54089ecfb2659c
  4. 6b2a491e4be23750908e7a7786b3b5e5c6a24b6f5edde2b77ae4aa15658e88cf
  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.