Tokenswim Attestations

Proof

84877f9b-2780-46b8-a4d3-a83080fe384d

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
c8c855dfd45ffe48a897dbf907abb2708cc05f8665047972ce17b72b860a26b5
Server digest
62bd456c9ff24829a0ad5306910e6d8affb6a905c61090866906633a72c5b72a
Client windows
[24612, 24740) [126097, 126225) [160444, 160572)
Server windows
[42052, 42180) [182654, 182782) [244160, 244288)
Drawn against
354915 client bytes · 319807 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
8406349e1fb40729031d1590fd8afe97cc68c527e0de247de5932077468bdd98
Leaf index
1235 of 1254
Audit path
  1. 7b0eca93e39307f84af4ca93da81236486c825c7a8d2f347684f873df790e1df
  2. 9fd86ff61c046644d0ae2ec71be1263d72d4ce765f417bb1d747d80845840a86
  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.