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

Merge pull #1191: Dev Docs: clarify null data conditions

Browse source 
Closes #1129
This commit is contained in:
David A. Harding 2016-02-10 09:03:46 -05:00
commit 661f8225c6
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7
2 changed files with 33 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

33
_includes/devdoc/guide_transactions.md
View file

@ -426,10 +426,22 @@ Signature script: <sig>
{% autocrossref %}
[Null data][/en/glossary/null-data-transaction]{:#term-null-data}{:.term} pubkey scripts let you add a small amount of arbitrary data to the block
chain in exchange for paying a transaction fee, but doing so is discouraged.
(Null data is a standard pubkey script type only because some people were adding data
to the block chain in more harmful ways.)
[Null data][/en/glossary/null-data-transaction]{:#term-null-data}{:.term}
transaction type relayed and mined by default in Bitcoin Core 0.9.0 and
later that adds arbitrary data to a provably unspendable pubkey script
that full nodes don't have to store in their UTXO database. It is
preferable to use null data transactions over transactions that bloat
the UTXO database because they cannot be automatically pruned; however,
it is usually even more preferable to store data outside transactions
if possible.
Consensus rules allow null data outputs up to the maximum allowed pubkey
script size of 10,000 bytes provided they follow all other consensus
rules, such as not having any data pushes larger than 520 bytes.
Bitcoin Core 0.9.x to 0.10.x will, by default, relay and mine null data
transactions with up to 40 bytes in a single data push and only one null
data output that pays exactly 0 satoshis:
{% endautocrossref %}
@ -438,6 +450,19 @@ Pubkey Script: OP_RETURN <0 to 40 bytes of data>
(Null data scripts cannot be spent, so there's no signature script.)
~~~
Bitcoin Core 0.11.x increases this default to 80 bytes, with the other
rules remaining the same.
It is expected that Bitcoin Core 0.12.0 (not released yet) will default
to relaying and mining null data outputs with up to 83 bytes with any
number of data pushes, provided the total byte limit is not exceeded.
There must still only be a single null data output and it must still pay
exactly 0 satoshis.
The `-datacarriersize` Bitcoin Core configuration option allows you to
set the maximum number of bytes in null data outputs that you will relay
or mine.
#### Non-Standard Transactions
{% include helpers/subhead-links.md %}