joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-26 17:26:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Content - Update Tx malleability

Browse source
This commit is contained in:
thephez 2018-09-28 11:09:47 -04:00
parent 7469ab4281
commit 6c7609f137
No known key found for this signature in database
GPG key ID: BBC8A06DBE236099
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
_includes/devdoc/guide_transactions.md
View file

@ -756,6 +756,14 @@ be added to the block chain immediately. But it does become a problem
when the output from a transaction is spent before that transaction is
added to the block chain.
Dash Core 12.3 implemented [BIP-147: Dealing with dummy stack element malleability](https://github.com/bitcoin/bips/blob/master/bip-0147.mediawiki)
which fixes a design flaw in OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY that
caused them to consume an extra stack element ("dummy element") after signature
validation. Previously, the dummy element was not inspected in any manner, and could be
replaced by any value without invalidating the script. BIP147 removed this
malleability vector by forcing the dummy element to be an empty byte array and
rejecting anything else.
<!-- Not applicable to Dash
Bitcoin developers have been working to reduce transaction malleability
among standard transaction types, one outcome of those efforts is
@ -786,4 +794,8 @@ in a way that invalidates the lost transaction. One method which will
always work is to ensure the reissued payment spends all of the same
outputs that the lost transaction used as inputs.
For additional information regarding the types transaction malleability,
reference [this blog post](https://blog.dash.org/segwit-lighting-rbf<!--noref-->-in-dash-9536868ca861)
by one of the Dash Core developers.
{% endautocrossref %}