From 7e878784bdba51a50f6cacf4622fff4f608245c5 Mon Sep 17 00:00:00 2001 From: thephez Date: Thu, 25 Oct 2018 16:23:49 -0400 Subject: [PATCH] Correct appendix reference --- dip-0003.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dip-0003.md b/dip-0003.md index e578a2c..67bce9f 100644 --- a/dip-0003.md +++ b/dip-0003.md @@ -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.