Tokenswim Attestations

Proof

81e646b0-2525-41ab-9960-62e463c01ee8

provedThe proof has been verified on-chain.
Upstream host
chatgpt.com
Certificate fingerprint
fa5ab82b6c558273ad37b3d6ef16c1be1125fee722c13ca2ab949b507c9fee38
Claimed model
gpt-5.6-terra
Session at
Client digest
0fa61651842981bbe76e7957039d90bd6ef52ffe56be358d197d93b3282d1728
Server digest
7255b3ea1817d72d678be559b3b8ee4dbd763fec34809abf063db6be3cbc9ff0
Client windows
[334299, 334427) [371283, 371411) [830742, 830870)
Server windows
[165606, 165734) [177476, 177604) [315416, 315544)
Drawn against
1105282 client bytes · 318584 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
ae6e550526430dab5f6c746820f56ae6f945172f53c8405a1a801d186ffb4884
Leaf index
1214 of 1219
Audit path
  1. 446a4213ee3b67171599f6de8c987bfcf1a56a6b0349ae8adbe781de5321e735
  2. b73447e238ebbb98539846a7e6798767453c0ba42c9df25eaa9db5fa0d826a56
  3. 59cc74468af994edf467a1235880dda35f5b4299a6facd0ed2adb39d77698721
  4. da9483448953dc44eb638b62447702be02426b7758d4420d671bd17ad1a8f44d
  5. 213b271b4665b5e97bd86196d89ac2ba2c91f9812a5015bf1efecae9a7d254d5
  6. 6d38306fb414141a855b719052e3db207fdc749f00a65de1f445e49d0bc052dd
  7. c59a7b18d61351c80007ffb30ddc6f55569ab3bcc2d61b4c3f67d359f9690b22
  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.