Skip to content

Commit

Permalink
docs(dip31): update masternode to evonode
Browse files Browse the repository at this point in the history
  • Loading branch information
thephez committed Oct 21, 2024
1 parent 31612ab commit c9eed2b
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions dip-0031.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ system and introduced in Protocol Version `70235`.

| Field | Type | Size(bytes) | Description |
| ----- | ----- | ----- | ----- |
| protxHash | uint256 | 32 | The protxHash of the masternode being banned |
| protxHash | uint256 | 32 | The protxHash of the evonode being banned |
| signedHeight | int32_t | 4 | The height at which this message was signed by the platform quorum |
| quorumHash | uint256 | 32 | The quorumHash of the quorum which signed the message |
| blsSignature | byte[] | 96 | The BLS signature over the message, by the quorum identified by quorumHash |
Expand All @@ -68,7 +68,7 @@ When received, a node must validate the message. It should do this by:
1. Check if the node is synced
* Penalty: skip validation of message, do not forward, do not mark as received in inventory
2. Validate the protxHash is in the masternodeList
* Penalty: small P2P penalty (1), as the masternode may have very recently been removed
* Penalty: small P2P penalty (1), as the evonode may have very recently been removed
3. Validate the masternode associated with the protxHash is an evonode and not a regular masternode
* Penalty: Ban node, P2P penalty (100)
4. Validate the signedHeight is valid and not too far in the past or future
Expand All @@ -92,7 +92,7 @@ During subsequent DKG sessions, masternodes should `voteBad` against members mar
`PlatformPoSeBanned`. If, during the DKG session, `quorumDkgBadVotesThreshold` (as defined by
[DIP-6](https://github.com/dashpay/dips/blob/master/dip-0006.md)) members vote to indicate a member
is bad, it will be prevented from participating in the quorum, resulting in a PoSe penalty bump and
potentially a PoSe Ban. The flag `PlatformPoSeBanned` must be set to false when a masternode is
potentially a PoSe Ban. The flag `PlatformPoSeBanned` must be set to false when an evonode is
[revived](https://github.com/dashpay/dips/blob/master/dip-0003.md#updating-service-features-from-operator-proupservtx)
in the deterministic masternode list (DML).

Expand Down

0 comments on commit c9eed2b

Please sign in to comment.