Communities governed by consensus may occasionally be compelled to plan for significant events that can affect the mechanism of government itself. As such, it is worth discussing whether qualifying significant events merit an elevated level of scrutiny and participatory notice. This unique mechanism is presented for discussion here as a “Referendum Ballot.”
A "Referendum Ballot " or vote meeting certain criteria would be created and scheduled, with a minimum 48 hour and maximum 14 day voting period. The ballot completes successfully at the end of the voting period when the minimum quorum has voted. An affirmative outcome triggers a smart contract that sets a date / time period for a future event. Examples of a future event include a “Hard Fork” that fundamentally changes blockcahin participation, or an election that demands advanced notice and maximum opportunity for voter participation to decide an event at a specific election date and limited time period. This “Referendum Ballot” mechanism solves potential communications and time-frame issues.
Example Referendum ballot for discussion: - Ballot is created with 48 hour voting window - description of the ballot: “let’s have a hard fork + 14 days from today, requiring all node participants to upgrade and verify on or before that date or be dropped from consensus.” Upon successful ballot approval, hard fork configs can be added and must be in place on or before the approved event (+14 days from end of ballot). Validator nodes that do not participate (having had 14 days notice of necessary code update) are removed, at least temporarily, from consensus, and network integrity is maintained.
Interested in the community response and ongoing discussion.
Respectfully submitted for review by Jim O’Regan, January 20, 2018