Tokenswim Attestations

Proof

341780e1-e252-4502-b06e-7db972596b3c

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-luna
Session at
Client digest
35bf798d0839e656d05756e211f3926d60db6aae49f4735384b15f4bbd34cfb5
Server digest
a6167ecb2d2e5b277df11c4bd14a159e9ea1fc0c320cd5a220f3570020cfcaf1
Client windows
[234, 362) [945, 1073) [2603, 2731)
Server windows
[9806, 9934) [10351, 10479) [15098, 15226)
Drawn against
2837 client bytes · 15729 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
bd9602d9f4db2ea22ceb0959ea965b947cf2b877925418e063b7e79c24e3cf67
Leaf index
1254 of 1257
Audit path
  1. 5b95853a3ac8379d7b62c09d318c5a54b68712659d9bcb967abcfd38e65e6ad2
  2. f5abcf8954213d425104d3387a30194dae4ee010f7c9adca9dfe06fe1b0b47b0
  3. b7a215cc9e5d6b56c0be44b71ae89fb5d64c5127aff4547dc86ba01f8299833a
  4. 5247553f3c3c1542d5344d32425e9099e5a0725012752b2b7eb1ad1e315df1cd
  5. 3f1b7307e26cb2d3b68fa0129c9384afcb1b676161162558cf579748d4967e33
  6. ee15c2c6367bbe862ede633674f1c8e0ec11f544c3482e36381d215559838be9
  7. 042dd7f38d4c4574b5c0582fdc65b11f79af6c1a9fecb526af92b88aee61bfa3
  8. 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.