mirror of https://github.com/zcash/zips.git
Clarify that coinbase spending restrictions only apply to transparent outputs
This commit is contained in:
parent
83e8313045
commit
84bbeaaed4
15
zip-0213.rst
15
zip-0213.rst
|
@ -72,13 +72,16 @@ Once the Heartwood network upgrade activates:
|
|||
- The consensus rules applied to ``valueBalance``, ``vShieldedOutput``, and ``bindingSig``
|
||||
in non-coinbase transactions MUST also be applied to coinbase transactions.
|
||||
|
||||
- The existing consensus rule requiring transactions that spend coinbase outputs to have
|
||||
an empty ``vout``, is amended to only apply to transactions that spend transparent
|
||||
coinbase outputs.
|
||||
- Only transparent outputs in coinbase transactions are subject to the existing
|
||||
restrictions on spending coinbase funds. More precisely:
|
||||
|
||||
- The existing consensus rule requiring coinbase outputs to have 100 confirmations before
|
||||
they may be spent (coinbase maturity), is amended to only apply to transparent coinbase
|
||||
outputs.
|
||||
- The existing consensus rule requiring transactions that spend coinbase outputs to have
|
||||
an empty ``vout``, is amended to only apply to transactions that spend transparent
|
||||
coinbase outputs.
|
||||
|
||||
- The existing consensus rule requiring coinbase outputs to have 100 confirmations
|
||||
before they may be spent (coinbase maturity), is amended to only apply to transparent
|
||||
coinbase outputs.
|
||||
|
||||
- Full Sapling note decryption MUST succeed using the all-zero outgoing viewing key. More
|
||||
precisely, all Sapling outputs in coinbase transactions MUST have valid note commitments
|
||||
|
|
Loading…
Reference in New Issue