Tokenswim Attestations

Proof

42f3fa57-8850-4462-a103-7895eac16cd1

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
5a6d71e54b249d1333bd16be6ff515cb46beda808011f3cd1f18dd3903aa4301
Server digest
90bb1619366e6c8a72bbcdbe3595bae0ba63fccdf8b6521f408f7e0f10f02a17
Client windows
[81645, 81773) [321850, 321978) [530327, 530455)
Server windows
[24233, 24361) [129840, 129968) [233310, 233438)
Drawn against
710737 client bytes · 313923 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
1b9511e00a0a409e9a9ea54a99055a7ca86335311501d119cd2bc738bdbed96a
Leaf index
1197 of 1219
Audit path
  1. 871bfa4c3b66e70706571716044b85983957b3723ef1d861ebd4c62d9de92b85
  2. f05bdaa2ec5bb67efb5332b95294cad8b20a52afdaebda38454bb498a3f64a29
  3. 2545811dad560b3766b52b208969ceea09a14f20dffb1e779cc358f9cb6694fb
  4. d80a94ce8940585f2c5b9bf7d5a584a70e594057e9574e002e0faf8deaecd750
  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.