set minimum participation threshold

KomodoPlatform · Jul 14, 2023 · 7835192 · 7835192
1 parent 345f92b
commit 7835192
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/doc/bible.md b/doc/bible.md
@@ -393,8 +393,8 @@ Once a DIP has been submitted:
  - Votes are allocated 1:1 for each address used to run a main server notary node, for each season it was in use.
  - Votes are to be cast via a signed message, generated by the address used in a notary's main notary node, for each season in was in use.
  - The vote schedule will be determined by a consensus of current DEV node notaries, with respect to the nature of the proposed changes and the time remaining until a hardfork.
- - Votes which attract less than 33% participation will be considered invalid, and the proposal rejected.
- - Votes which attract greater than 33% but less than 50% participation will be require a 2/3rds majority to be considered valid. If this threshold is not acheived, the proposal will be reset and a new vote scheduled.
+ - Proposals which only attract 20 votes or less will be considered invalid, and the proposal rejected.
+ - Votes which attract at least 21 votes, but less than 33 votes will require a 2/3rds majority be considered valid. If this threshold is not acheived, the proposal will be reset and a new vote scheduled.
 
 
 Signed messages must conform to the following format to be considered valid: