Maker UX idea board

Introduce the MVP for vote delegation. Vote delegation will be split in: MVP Version 1 Version 2 The first MVP will include the ability to delegate and undelegate, to create a delegate contract and see recognized and shadow delegates. The data for the delegates is pulled from on-chain information, spock and the community repo.

It would be nice to have a way more detailed breakdown of the governance polls. Today, I'm using the MCD Voting Tracker to try and get some insights, but that one doesn't count votes correctly. Voting is a pretty serious affair in organizations, so many people will have questions who voted what on which proposals, whether the voting control is centralized, etc. The voting portal today lacks this information. A similar breakdown can be provided for delegators (they're not voting on proposals, but they are voting on delegates.)

The team is in contact with the EPNS (Ethereum Push Notification Service) team to work on important governance notifications. New executive votes New polling votes New executive vote becomes the hat Important votes finishing soon Big change on voting percentage in a quick timespan (suddenly spike in a vote) Subscribe to an address votes (get notified when a delegate or certain address vote on something) User subscribe to a poll/executive, get notified when it finishes or when there's a new vote Notify when a delegate contract is expiring ( 1 week before / 1 month before) executive cast versus schedule (after GSM delay when it affects the protocol ) Your delegate hasn't voted in 1 month / 2 month Vote is replaced Unrecognized executive gains MKR Unrecognized executive becomes the hat MKR enters in the ESM Please add comments to include more relevant ideas.

Kovan is being discontinued by the Maker team, we need to start to support Goerli in our systems. This will include: Migrating dai.js support to goerli Creating the testchain changes for goerli Allowing goerli on the governance UI Creating test accounts for the team

For polls and executives

Currently voting as an individual is impossible when a delegate contract is active

Approval voting means that people can put their weight behind multiple options. Approval is good to rank a set of options (our main usecase would be prioritisation eg.) LFW: It's mainly useful when we want to rank a set of options in order of priority. Ironically ranked choice isn't great for that. Because it moves the vote weight around to find the best option. Ranked choice is good to choose a single option from a set of valid options. NOTE: No need to progress beyond time estimate until we know more from govalpha

instead of going to the main ballot page

As suggested by govalpha

Add a visual multi-step onboarding process similar to tools like Miro. Explain the basics of 1) the Maker governance process and 2) the voting portal functionalities.

The challenge would be to not feel limited by the processes and infrastructure in place today. This would be a project with a longer time-horizon and would involve collaborations with other CUs.

Link to more specific and relevant content vs the current generic list

Inspired by https://daistats.goatcounter.com/ Leverage open-source infra AND make the dashboard publicly accessible.