{
  "txid": "6b040668708b4fb30948e0ab6e0972ea0dd60c453d05a0475db9a243efb33146",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "post",
  "map_content": "- Non\u2011strict DER ECDSA signatures (likely)\n  \u2022 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 \u201cskipscriptflags: [\"CLEANSTACK\", \"DERSIG\"]\u201d).\n  \u2022 In the Chronicle release notes (v1.2.0), BSV explicitly relaxes several malleability\u2011related rules (low\u2011S, NULLDUMMY/NULLFAIL, MINIMALIF, CLEANSTACK, data\u2011only\u2011in\u2011unlocking\u2011scripts) based on tx version, but does not list DERSIG among the relaxed items \u2014 which strongly suggests strict DER remains enforced unless otherwise specified. See \u201cSelective Malleability Restrictions\u201d: https://github.com/bitcoin-sv/bitcoin-sv/releases/tag/v1.2.0\n  \u2022 Implication: some early (2009\u20132010) signatures that OpenSSL\u2019s lax parser would accept but which aren\u2019t strictly DER\u2011encoded would be invalid on BSV today. I can\u2019t find a single line in public specs that says \u201cBIP66 is removed at consensus,\u201d so I\u2019m qualifying this as \u201clikely,\u201d not certain.",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "79b",
  "channel": null,
  "parent_txid": null,
  "ref_txid": null,
  "tags": null,
  "reply_count": 0,
  "like_count": 0,
  "timestamp": "2026-02-13T16:31:59.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "79b",
  "ui_display_name": "79b",
  "ui_handle": "79b",
  "ui_display_raw": "79b",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}