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

Dev Docs: Update description of P2SH standardness

Browse source 
Closes #1052
This commit is contained in:
David A. Harding 2015-09-07 10:12:47 -04:00
parent d8bc6626f4
commit 47b255e888
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7
2 changed files with 6 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

13
_includes/devdoc/guide_transactions.md
View file

@ -452,14 +452,11 @@ receive an error.
If you create a redeem script, hash it, and use the hash
in a P2SH output, the network sees only the hash, so it will accept the
output as valid no matter what the redeem script says.
This allows
payment to non-standard pubkey script almost as easily as payment to
standard pubkey scripts. However, when you go to
spend that output, peers and miners using the default settings will
check the redeem script to see whether or not it's a standard pubkey script.
If it isn't, they won't process it further---so it will be
impossible to spend that output until you find a miner who disables the
default settings.
This allows payment to non-standard scripts, and as of Bitcoin Core
0.11, almost all valid redeem scripts can be spent. The exception is
scripts that use unassigned [NOP op codes][]; these op codes are
reserved for future soft forks and can only be relayed or mined by nodes
that don't follow the standard mempool policy.
Note: standard transactions are designed to protect and help the
network, not prevent you from making mistakes. It's easy to create