From 0d09d80194ca7ecd6d1d81f28a7106b449b5139e Mon Sep 17 00:00:00 2001 From: Kamuela Franco Date: Mon, 1 Oct 2018 14:19:28 +0100 Subject: [PATCH] Clarify word choice (#17) DIP-3 updated --- dip-0003.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dip-0003.md b/dip-0003.md index b3a3a33..3e46f93 100644 --- a/dip-0003.md +++ b/dip-0003.md @@ -71,8 +71,8 @@ To join the masternode list, masternode owners must submit a special transaction The ProRegTx contains 3 public key IDs, which represent 3 different roles in the masternode and define update and voting rights. A "public key ID" refers to the hash160 of an ECDSA public key. These are: - 1. KeyIdOwner: This is the public key ID of the masternode or collateral owner. It is different than the key used in the collateral output. The owner is only allowed to issue ProUpRegTx transactions. - 2. KeyIdOperator: This is the public key ID of the masternode operator. The operator is only allowed to issue ProUpServTx transactions. The operator key is also used while operating the masternode to sign masternode related P2P messages, quorum related messages and governance trigger votes. Messages signed with this key are only valid while the masternode is in the valid set. + 1. KeyIdOwner: This is the public key ID of the masternode or collateral owner. It is different than the key used in the collateral output. Only the owner is allowed to issue ProUpRegTx transactions. + 2. KeyIdOperator: This is the public key ID of the masternode operator. Only the operator is allowed to issue ProUpServTx transactions. The operator key is also used while operating the masternode to sign masternode related P2P messages, quorum related messages and governance trigger votes. Messages signed with this key are only valid while the masternode is in the valid set. 3. KeyIdVoting: This is the public key ID used for proposal voting. Votes signed with this key are valid while the masternode is in the registered set. A single key can be used for multiple roles so the owner can also operate the masternode and/or issue proposal votes. Alternately, different keys can be used to delegate duties to other people. For example, owners might decide to use a masternode hosting service instead of self-hosting the masternode. To do so, they would use the operator key provided by the hosting service. The same applies to the voting key, which allows them to assign voting rights to someone else.