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

Dev Docs: Update IsStandard ScriptSig Size For BCC 0.9.3/10.0.0

Browse source 
Also fix a few other minor issues in that section.

Thanks to gsalgado for reporting this!  Closes #705
This commit is contained in:
David A. Harding 2015-01-08 10:36:26 -05:00
parent ddbc448553
commit 2d46b41e3e
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7
3 changed files with 13 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
_autocrossref.yaml
View file

@ -59,6 +59,8 @@ coinbase field:
compactsize uint: compactsize unsigned integer
compactsize unsigned integer:
compactsize unsigned integers: compactsize unsigned integer
compressed public key:
compressed public keys: compressed public key
confirm:
confirmed:
confirmation:

16
_includes/guide_transactions.md
View file

@ -467,7 +467,7 @@ Note: standard transactions are designed to protect and help the
network, not prevent you from making mistakes. It's easy to create
standard transactions which make the satoshis sent to them unspendable.
As of Bitcoin Core 0.9, standard transactions must also meet the following
As of Bitcoin Core 0.9.3, standard transactions must also meet the following
conditions:
* The transaction must be finalized: either its locktime must be in the
@ -478,9 +478,11 @@ conditions:
times larger than a typical single-input, single-output P2PKH
transaction.
* Each of the transaction's inputs must be smaller than 500 bytes.
That's large enough to allow 3-of-3 multisig transactions in P2SH.
Multisig transactions which require more than 3 public keys are
* Each of the transaction's signature scripts must be smaller than 1,650 bytes.
That's large enough to allow 15-of-15 multisig transactions in P2SH
using compressed public keys.
* Bare (non-P2SH) multisig transactions which require more than 3 public keys are
currently non-standard.
* The transaction's signature script must only push data to the script
@ -488,8 +490,10 @@ conditions:
OP codes which solely push data to the stack.
* The transaction must not include any outputs which receive fewer than
the defined minimum number of satoshis, [currently 546][bitcoin core
fee drop commit].
1/3 as many satoshis as it would take to spend it in a typical input.
That's [currently 546 satoshis][bitcoin core fee drop commit] for a
P2PKH or P2SH output on a Bitcoin Core node with the default relay fee.
Exception: standard null data outputs must receive zero satoshis.
{% endautocrossref %}

1
_includes/references.md
View file

@ -35,6 +35,7 @@ http://opensource.org/licenses/MIT.
[coinbase field]: /en/developer-reference#term-coinbase-field "A special input-like field for coinbase transactions"
[coinbase transaction]: /en/developer-reference#term-coinbase-tx "A special transaction which miners must create when they generate a block"
[compactsize unsigned integer]: /en/developer-reference#compactsize-unsigned-integers "A type of variable-length integer"
[compressed public key]: /en/developer-guide#public-key-formats "A public key that is 33 bytes long rather than the 65 bytes of an uncompressed public key"
[confirm]: /en/developer-guide#term-confirmation "A transaction included in a block currently on the block chain"
[confirmed]: /en/developer-guide#term-confirmation "A transaction included in a block currently on the block chain"
[confirmed transactions]: /en/developer-guide#term-confirmation "Transactions included in a block currently on the block chain"