Tokenswim Attestations

Proof

0b123142-f423-4344-81de-26354a25cf68

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
154042556ed17c545c2d21a3bc5ffcbddc385115b9884a5f6017a6b103a68964
Server digest
0067c7e53e1fbd6e1cd30c737e2ebb63fd9d11f5a4f3ae42c45fef328d3ba3e9
Client windows
[161961, 162089) [354944, 355072) [389253, 389381)
Server windows
[149436, 149564) [254780, 254908) [311639, 311767)
Drawn against
419692 client bytes · 352639 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
bdb4ae935f0abe38aaed5aef530749060bc01bc71a49defb8ea58bf01dbd0362
Leaf index
1232 of 1254
Audit path
  1. f372b525d5843c54095186f9e29fb0e14091f7b3e3ac0fc7ec73a181ff92c650
  2. 67f2658f307cfec55f9ae1ff0ba5b2af773a47b3e3be41bcd0fadbc2ed87880c
  3. c7b318e717ab00b95c16ae491d3ed4e720ed916db826af156e28cc0534b3f79e
  4. 976077627aaf0b69e62d0b49cb4755d31e4dd787aded7d44fc2596ad1ce78246
  5. 43525f3f94a524696ae952ad3dcfe89a60d6d86f3575e9afc267a1006bd22c50
  6. 2bc917ad681c543c4f8c858664f8bc1f1d3f8e147ca119a9c5d5eaebcf5b1430
  7. ee15c2c6367bbe862ede633674f1c8e0ec11f544c3482e36381d215559838be9
  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.