mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 01:36:13 +00:00
Set license files and headers for bitcoin.org's content
This commit is contained in:
parent
27f1da3ba8
commit
2a139a51a1
276 changed files with 524 additions and 171 deletions
|
@ -1,3 +1,8 @@
|
|||
{% comment %}
|
||||
This file is licensed under the MIT License (MIT) available on
|
||||
http://opensource.org/licenses/MIT.
|
||||
{% endcomment %}
|
||||
|
||||
## Transactions
|
||||
|
||||
The following subsections briefly document core transaction details.
|
||||
|
@ -63,7 +68,7 @@ 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]
|
||||
|
||||

|
||||

|
||||
**<span id="signature_script_modification_warning">Signature script modification warning</span>:**
|
||||
Signature scripts are not signed, so anyone can modify them. This
|
||||
means signature scripts should only contain data and data-pushing op
|
||||
|
@ -73,7 +78,7 @@ 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.)
|
||||
|
||||

|
||||

|
||||
**`OP_CHECKMULTISIG` warning:** The multisig verification process
|
||||
described above requires that signatures in the signature script be
|
||||
provided in the same order as their corresponding public keys in
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue