Tokenswim Attestations

Proof

332975ea-51b8-40a0-b46c-689cffa43548

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
8c7146f2641cce2126589aa07f6311ddaafc2009ba961bd11ca8e75c497d596b
Server digest
fc49522568d16d8fbc0e03804fb6266d5ffa8da91d922e1118c5e174987d6780
Client windows
[172205, 172333) [186169, 186297) [199077, 199205)
Server windows
[141349, 141477) [214803, 214931) [270728, 270856)
Drawn against
406807 client bytes · 371574 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
f5e048b74c9456e78edf5dc534a47095d3dbeef769ebc208adf30fe517d72e90
Leaf index
1230 of 1254
Audit path
  1. 619e7b25f3b21a9491e9f5b5ece2991c10069ed403b2e95631cc82cde4a2766d
  2. f4b4978f1f2d461ee9b2c3ef585ab34a392cb8727fdaaf5d595867e26cacca7f
  3. af92278378eec67a97073ecf12654d5510423211372efa182ae8b0d4745c2d42
  4. 7ad9ffba38bde7f97c35d2735d6a1aab069a51c719c1c8a45e440719625496e2
  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.