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

Revise Note About Op Codes In Signature Scripts (closes #563)

Browse source 
Based on text and revisions by @petertodd and @luke-jr in pull #563.
This commit is contained in:
David A. Harding 2014-10-23 16:00:53 -04:00
parent 5959721141
commit 1061571b13
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
_includes/ref_transactions.md
View file

@ -52,10 +52,13 @@ A complete list of OP codes can be found on the Bitcoin Wiki [Script
Page][wiki script], with an authoritative list in the `opcodetype` enum
of the Bitcoin Core [script header file][core script.h]
Note: non-standard transactions can add non-data-pushing op codes to
their signature script, but signature scripts are run separately from the pubkey scripts (with a
shared stack), so signature scripts can't use arguments such as `OP_RETURN` to
prevent the script from working as expected.
Note: Signature scripts are not signed, so anyone can modify them. This
means signature scripts should only contain data and data-pushing op
codes which can't be modified without causing the pubkey script to fail.
Placing non-data-pushing op codes in the signature script currently
makes a transaction non-standard, and future consensus rules may forbid
such transactions altogether. (Non-data-pushing op codes are already
forbidden in signature scripts when spending a P2SH pubkey script.)
{% endautocrossref %}