Author: Aymeric Vitte 2019-05-03 09:51:25
Published on: 2019-05-03T09:51:25+00:00
In a recent bitcoin-dev discussion, Aymeric Vitte sought to clarify the standardness of bitcoin scripting. Specifically, he was unsure if nodes would relay non-usual transactions and how to determine what they will accept. The consensus among contributors is that any custom script can be wrapped in P2SH and P2WSH and it will be propagated. P2PKH and P2WPKH cannot have custom scripts. However, once a claim on a modified x-of-3 is propagated, the redeemScript is known and someone can attempt to RBF with a modified witness stack or scriptSig to claim the UTXO. As for BCH, its standardness is unclear since it is based on bitcoin code unless they changed the policy. Contributors were unsure whether the story that nodes would not propagate the fix or that people did not want to take the risk to propagate it was true. Also discussed were SHA bounties which were propagated before `isStandard`, and can still be propagated today if they are wrapped in a P2SH or P2WSH, but the `redeemScript` must be published by some other method or bribed by a miner if it's not time-sensitive. In response to Aymeric’s query, James Prestwich shared a reference for default TX_NONSTANDARD policies in v0.18. He adds that documenting standardness is sisyphean as it varies from version to version. His reference applies only to v0.18 and may already be outdated.
Updated on: 2023-06-13T18:29:40.353754+00:00