RIP-000-004: Add Snapshot as a signaling mechanism for RIPs

Full support from the community!

To not delay accepting this RIP now, we will also directly accept the comments from the community, as they all agree that a Snapshot vote needing to be 7 days is too long. Since we still want proposals to exist for at least 7 days overall from the time of inception to getting accepted or rejected (a precaution against governance attacks), a simple compromise is to require that anytime a RIP is proposed, it should at least bake for 3 days on the forum through discussion with community members, and modified if need be, before the Snapshot poll is put up.

The Snapshot poll should then have the voting duration of 96 hours (4 days) instead.

To summarise: 3 days (or more if needed) of discussion on the forum, and 4 days for the Snapshot poll.

And as always, these parameters can always be changed by the community through a proposal, which is easier now with the Snapshot tool!

And for any new proposal now, to make it simpler when deciding on whether a RIP should be accepted while it could have a parameter set at different values (e.g. how long a Snapshot vote should be), a Snapshot poll can include multiple ‘yes’ alternatives with the different parameter values, e.g:

  • yes - 7 days
  • yes - 6 days
  • yes - 5 days
  • no

Where all the different ‘yes’ votes in aggregate count as ‘yes’ (unless specified differently by the proposal).


I will now edit the Ren Governance Process document so that one always can find the current governance process there, and the community is now free to set up Snapshot votes when you create an RFC/RIP or for any other governance-related matter.

4 Likes