Merge pull request #24 from dashpay/thephez-patch-1

Correct appendix reference
This commit is contained in:
Nathan Marley 2018-10-26 10:36:48 -05:00 committed by GitHub
commit da7f9a83c3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -170,7 +170,7 @@ If an operator suspects their keys are insecure or if they wish to terminate ser
When a ProUpRevTx is processed, it updates the metadata of the masternode entry by removing the operator and service information and marks the masternode as PoSe-banned. Owners must later issue a ProUpRegTx Transaction to set a new operator key. After the ProUpRegTx is processed, the new operator must issue a ProUpServTx Transaction to update the service-related metadata and clear the PoSe-banned state (revive the masternode).
Appendix B describes potential reasons for a revocation.
[Appendix A](#appendix-a-reasons-for-self-revocation-of-operators) describes potential reasons for a revocation.
The special transaction type used for Provider Update Revoking Transactions is 4.