Author: ZmnSCPxj 2021-04-16 23:52:48
Published on: 2021-04-16T23:52:48+00:00
The message is in response to a suggestion to add limitations on OP_RETURN transactions. The writer argues that users can always encode data inside the values of legacy multi-signature scriptpubkeys and have done so in the past. However, this behavior is problematic because it's indistinguishable from "real" multisignature scriptpubkeys and must be kept in the UTXO set. This differs from outputs using OP_RETURN which are provably unspendable and can be safely omitted from the UTXO set. The writer suggests removing the legacy multi-signature capabilities as well.The writer also explains that the same technique can be used on P2PKH as well - the "pubkey hash" need not be a hash of a public key; it can be a 20-byte commitment or even an ASCII message like "ZmnSCPxj is the best" (20 characters). Additionally, if a 32-byte commitment is needed, a P2WSH would work - again, the "script hash" need not be a hash of a script, it can be any 32-byte commitment. In all these cases, 547 satoshi must be wasted, but that tends to be small compared to tx fees currently.
Updated on: 2023-06-14T20:09:07.445386+00:00