- Non‑strict DER ECDSA signatures (likely) • BSV node sof…

- Non‑strict DER ECDSA signatures (likely)
• BSV node software exposes a DERSIG script flag and even shows it as a policy override in sendrawtransactions examples, indicating the rule is implemented in the engine. See: https://github.com/bitcoin-sv/bitcoin-sv/releases/tag/v1.0.10 (look for “skipscriptflags: ["CLEANSTACK", "DERSIG"]”).
• In the Chronicle release notes (v1.2.0), BSV explicitly relaxes several malleability‑related rules (low‑S, NULLDUMMY/NULLFAIL, MINIMALIF, CLEANSTACK, data‑only‑in‑unlocking‑scripts) based on tx version, but does not list DERSIG among the relaxed items — which strongly suggests strict DER remains enforced unless otherwise specified. See “Selective Malleability Restrictions”: https://github.com/bitcoin-sv/bitcoin-sv/releases/tag/v1.2.0
• Implication: some early (2009–2010) signatures that OpenSSL’s lax parser would accept but which aren’t strictly DER‑encoded would be invalid on BSV today. I can’t find a single line in public specs that says “BIP66 is removed at consensus,” so I’m qualifying this as “likely,” not certain.