[RFC] Better Governance Process communication for Hop DAO



I previously raised a discussion on the forum (here:Enhancing Hop’s Operations with Syncvote - :speech_balloon:General Discussions - Hop) and received feedback to make a better illustration on the use case of my product for Hop community, so I decided to start this thread to make better presentation on how Hop DAO can benefit from Syncvote. If this is something interesting, I would like to take this to the Community Temperature Check.


The current governance process documentation is rather difficult to navigate for any average DAO member. I want to fix that using Syncvote (this is a product I am building) - the platform specifically designed to streamline workflows, facilitate decision-making, and ensure that every member’s input is considered.

My co-founder created a video to illustrate how the new presentation is better for Hop DAO to communicate the governance process and make it easier for admins to manage any future update of the process and help you easily comprehend the reasons behind this proposal and what lies ahead: Hop <> Syncvote Demo


As active members of our DAO, we understand the importance of reading and staying informed about various aspects of our organization. However, the extensive amount of information can sometimes be overwhelming.

It’s my belief that people often prefer a quick, concise overview of the processes, rather than having to delve into lengthy documents.

With this in mind, I propose a transformation of our current governance documents. We should aim to create a more intuitive and user-friendly workflow that provides a streamlined overview of our processes. This will not only make it easier for members to understand our DAO’s governance process but will also encourage broader participation and engagement.


I’ve already made a new presentation of Hop Governance Process and in the next step section below, I outline the actions needed for Hop DAO to adopt Syncvote.

Outcome expected:

I aim to transition from this lengthy and tedious text to more intuitive workflows, like the picture below.

Why is the new version of Syncvote better?

  1. User visualization: Users now know exactly where to start. They only need to focus on the steps relevant to them and don’t have to worry about the next steps if they’re not relevant.
  2. Future proof: Conditions for creating a proposal and ensuring its success have been separated into distinct fields, making it convenient for future automation.

Next Step

I propose to use our redesigned workflow as the official governance process document.

Next steps will be:

  1. Replace governance process docs by Syncvote’s redesign workflow. To be specific, the governance process will be put with a hyperlink. When community members click to this thread, it will lead them to Syncvote interface.

  2. Pin the link in Governance Guide in #resources channel in Discord:

  3. I will write a post to instruct people on governance process


The goal of this proposal is to improve the governance experience of the Hop’s community members. I fully respected the current governance process and did not make any change to it.

For me personally, I’ve been joining hundred of DAOs since I start develop Syncvote and I find Hop team is one of the most active and welcoming team, that’s why I would like to do my contribution to improve Hop community.

I would also be happy to update the workflow if there’s anything mismatched or missing; or transfer the editor right for you anytime.

The below response reflects the views of L2BEAT’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking and ideation of the two.

Does this RFC seek to just change the documentation of the governance process for Hop (found here), with the redesign workflow from Syncvote? Or does it also imply the adoption of Syncvote’s interface as outlined in your first post?

If the former, what would the operational and financial overhead for the DAO be?