Tokenswim Attestations

Proof

74aa529e-24fe-451a-a19b-eada041ee271

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
063d91e740c0108fc387e0337859877f948f99a8f72ac5e2af06c42b6f0ac810
Server digest
a0e89511dd3b5b3fc060f468f0506bf708f69d2e33ee6bfe96de909038710eb8
Client windows
[264703, 264831) [270284, 270412) [358575, 358703)
Server windows
[216120, 216248) [319769, 319897) [359092, 359220)
Drawn against
365877 client bytes · 383230 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
047208c1e1c87cd536f5074c4fddf73bf3b2fe88598fb23823ab21f4096b1e29
Leaf index
1221 of 1254
Audit path
  1. b27d9d7125d9fa703488af244bcacf44c6a583fb3b810f8f02d1a6472a25b28f
  2. d3ea311f1d4b50d2936a11d4cfc587f95cc352790d21f7c99d8bae8f0d1adf56
  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.