Tokenswim Attestations

Proof

7591adc7-4428-4e5c-b019-e89c8da697d8

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
0917ef3f9b82977085c905a0828080cfe713744a31058893ec7fc62c0ca47492
Server digest
58ecba19339841da364a5373733d83cba804b0cfeae63728ab4f3ab726be24c8
Client windows
[23843, 23971) [33527, 33655) [166709, 166837)
Server windows
[179437, 179565) [221411, 221539) [233026, 233154)
Drawn against
274721 client bytes · 252936 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
4fc1fe94acddd63b72ac8baaf372fc4a02bba2a5bdd7abfbb16524ad090f0dfe
Leaf index
1222 of 1254
Audit path
  1. 33d78f51185c6f1daa50c8c465eacd12f9efc3796d5203c20760a1f56a3f12c0
  2. 66914d9f19eddb2cee4b6abf2db9be25d67d77051a15adb54493a451abf8aae6
  3. 4b36a1232cb713a7e973c05345a0f4ed60f2437b23a720b61ddbc5bcac89ba3e
  4. e30d7a54690b0bf8ae07bd5716b7baad920e7775c32258780fa1725084899b18
  5. 400ec3b8c93beda26c7f6ebb07545bc39a821b6b5335dfd87904c2e010de7203
  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.