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

Correct appendix reference

Browse source
This commit is contained in:
thephez 2018-10-25 16:23:49 -04:00 • committed by GitHub
parent e19f4a5c4e
commit 7e878784bd
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
dip-0003.md
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). 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. The special transaction type used for Provider Update Revoking Transactions is 4.