Author: Chris Stewart 2018-06-06 00:17:52
Published on: 2018-06-06T00:17:52+00:00
Chris asked if there is a current use case for SIGHASH_NONE that would suffer from it being non-standard. Johnson Lau has made a pull request to add a new policy to disallow using SIGHASH_SINGLE without matched output, as it is insecure and could lead to theft of any UTXO of the same key in non-segwit scripts. This unintended consensus behavior is one of the earliest ones and these signatures are inherently unsafe, so Johnson believes it does no harm to disable this feature with a softfork. However, since these signatures are currently allowed, the first step is to make them non-standard.
Updated on: 2023-06-13T03:12:15.048841+00:00