Community Resolutions and Voting (RPIP-4)

This proposal does two things: - Formally introduces components that are already part of our snapshot and voting process (eg, quadratic scaling for power) - Provides a structure for how votes MUST flow and how they are RECOMMENDED to flow The rough outline is: - Proposals must have a post on the forums and demonstrate sufficient community interest (a poll is recommended) - Rocket Pool Core team (initially) starts a Snapshot vote that lasts at least 1 week, with 2 preferred - Votes require at least a 15% quorum, with a mechanism for quorum reduction if it’s consistently not met so the process doesn’t get stuck - Vote power is srqt(effective_RPL_stake) [this is currently implemented with a factor of 0.5; this is considered an inconsequential bug] - Voting should use basic voting (For/Against/Abstain), and whichever of For/Against has the most power wins - Voting MAY use other voting types, but doing so has to be in an accepted RPIP. I.e. to do this, a basic vote is required to confirm that “for this particular type of decision, we’ll use an alternative voting method.” - RPIP-4 also notes that there is a built-in veto because Snapshot is a signaling mechanism and someone needs to execute on the signal. There is text covering how that veto power should and should not be used.