Content - version bump

0.13.0.0 bumped to 70213 (dashpay/dash#2557)
This commit is contained in:
thephez 2018-12-17 09:28:24 -05:00
parent 7348fe59ba
commit 6a5a8f1213
No known key found for this signature in database
GPG key ID: BBC8A06DBE236099
3 changed files with 13 additions and 13 deletions

View file

@ -154,7 +154,7 @@ integer value used in P2P messages, and the actual Dash value.
| 3 | 8 | 00.0100001 |
| 4 | 16 | 00.00100001 |
Protocol version 70212 added a 5th denomination (0.001 DASH).
Protocol version 70213 added a 5th denomination (0.001 DASH).
The denominations are structured to allow converting between denominations
directly without requiring additional inputs or creating change (for example,
@ -169,7 +169,7 @@ directly without requiring additional inputs or creating change (for example,
**Creating Collaterals**
PrivateSend collaterals are used to pay mixing fees, but are kept separate from
the denominations to maximize privacy. Since protocol version 70212, the minimum
the denominations to maximize privacy. Since protocol version 70213, the minimum
collateral fee is 1/10 of the smallest denomination for all mixing sessions
regardless of denomination.
In Dash Core, collaterals are created with enough value to pay 4 collateral fees

View file

@ -66,7 +66,7 @@ with the most recent versions listed first. (If you know of a protocol
version that implemented a major change but which is not listed here,
please [open an issue][docs issue].)
As of Dash Core 0.13.0.0, the most recent protocol version is 70212.
As of Dash Core 0.13.0.0, the most recent protocol version is 70213.
| Version | Initial Release | Major Changes
|---------|------------------------------------|--------------
@ -548,7 +548,7 @@ to the `getheaders` message will include as many as 2,000 block headers.
{% autocrossref %}
*Added in protocol version 70212*
*Added in protocol version 70213*
The `getmnlistd` message is sent to request a full masternode list or an
update to a previously requested masternode list.
@ -883,7 +883,7 @@ template near the beginning of this subsection.
{% autocrossref %}
*Added in protocol version 70212*
*Added in protocol version 70213*
The `mnlistdiff` message is a reply to a `getmnlistd` message which
requested either a full masternode list or a diff for a range of blocks.
@ -1906,8 +1906,8 @@ is sent by masternodes to indicate approval of a transaction lock request
| 32 | txHash | uint256 | Required | TXID of the transaction to lock
| 36 | outPoint | outpoint | Required | The unspent outpoint to lock in this transaction
| 36 | outpointMasternode | outpoint | Required | The outpoint of the masternode which is signing the vote
| 32 | quorumModifierHash | uint256 | Required | *Added in protocol version 70212. Only present when Spork 15 is active.*<br><br>
| 32 | masternodeProTxHash | uint256 | Required | *Added in protocol version 70212. Only present when Spork 15 is active.*<br><br>The proTxHash of the DIP3 masternode which is signing the vote
| 32 | quorumModifierHash | uint256 | Required | *Added in protocol version 70213. Only present when Spork 15 is active.*<br><br>
| 32 | masternodeProTxHash | uint256 | Required | *Added in protocol version 70213. Only present when Spork 15 is active.*<br><br>The proTxHash of the DIP3 masternode which is signing the vote
| 96 | vchMasternodeSignature | char[] | Required | Masternode BLS signature
The following annotated hexdump shows a `txlvote` message. (The

View file

@ -427,7 +427,7 @@ transaction types is maintained in the [DIP repository](https://github.com/dashp
{% autocrossref %}
*Added in protocol version 70212 of Dash Core as described by DIP3*
*Added in protocol version 70213 of Dash Core as described by DIP3*
The Masternode Registration (ProRegTx) special transaction is used to join the
masternode list by proving ownership of the 1000 DASH necessary to create a
@ -585,7 +585,7 @@ ProRegTx Payload
{% autocrossref %}
*Added in protocol version 70212 of Dash Core as described by DIP3*
*Added in protocol version 70213 of Dash Core as described by DIP3*
The Masternode Provider Update Service (ProUpServTx) special transaction is used
to update the IP Address and port of a masternode. If a non-zero operatorReward
@ -658,7 +658,7 @@ ProUpServTx Payload
{% autocrossref %}
*Added in protocol version 70212 of Dash Core as described by DIP3*
*Added in protocol version 70213 of Dash Core as described by DIP3*
The Masternode Provider Update Registrar (ProUpRegTx) special transaction is used
by a masternode owner to update masternode metadata (e.g. operator/voting key
@ -739,7 +739,7 @@ ProRegTx Payload
{% autocrossref %}
*Added in protocol version 70212 of Dash Core as described by DIP3*
*Added in protocol version 70213 of Dash Core as described by DIP3*
The Masternode Operator Revocation (ProUpRevTx) special transaction allows an
operator to revoke their key in case of compromise or if they wish to terminate
@ -801,7 +801,7 @@ ProUpRevTx Payload
{% autocrossref %}
*Added in protocol version 70212 of Dash Core as described by DIP4*
*Added in protocol version 70213 of Dash Core as described by DIP4*
The Coinbase (CbTx) special transaction adds information to the blocks coinbase
transaction that enables verification of the deterministic masternode list without
@ -872,7 +872,7 @@ Coinbase Transaction Payload
{% autocrossref %}
*Added in protocol version 70212 of Dash Core as described by DIP6*
*Added in protocol version 70213 of Dash Core as described by DIP6*
The Quorum Commitment special transaction adds the best final commitment from a
Long-Living Masternode Quorum (LLMQ) Distributed Key Generation (DKG) session to