MakerDAO DUX Core Unit
Create
Log in
Sign up
Roadmap
Feedback
⭐️ Governance Portal requests
47
Boards
⭐️ Governance Portal requests
🗳 Governance process ideas
🐞 Bug reports
Powered by Canny
⭐️ Governance Portal requests
Please provide a detailed description of the desired feature/improvement and explain why it would be useful
Share your feedback...
Refactor delegate contracts
Refactoring the voteDelegate and voteDelegateFactory contracts in order to enable better UX regarding DVC strategies and renewal/expiry. In consultation with PE CU. Note that the DUX team cannot and will not write smart contracts.
1
·
under review
1
Add off-chain signing support for Safe multisigs
Up until now (Gnosis) Safe users were unable to interact with certain features due to a lack of support for off-chain signatures. The Safe team is currently working on adding EIP-1271 support which would enable us to re-enable these features for multisig users. Examples are gasless voting and easy delegate contract migration. Blocked until the Safe team releases this ticket. Context: https://github.com/safe-global/web-core/issues/1088
1
·
under review
1
Add pagination for long lists
Goal Add pagination where needed, as a means to moving the Governance Portal into a stable state wherein it can run for 1-2 years with minimal maintenance. Context The Governance Portal needs to be able to handle an ever-growing number of executives, polls and delegates without requiring maintenance. By adding pagination we make the app more robust and more user-friendly. To-Do Add pagination to delegates Add pagination to polls Add pagination to executives with lots of supporters (executive supporters) Add pagination to polls with lots of voters (poll vote breakdown)
1
·
planned
1
Improve UI for ranked choice polls
After a user's complaint we made small improvements to the UI for ranked choice polls. -- Add poll type indicator --Add tooltip explainer for ranked choice poll algorithm --Change colour schemes used to make transfers more distinct from first-choice votes in the vote breakdown UI. This got us thinking about ways to make the UI even more useful advanced. Some ideas that were surfaced: 1) Add a toggle for displaying/hiding transfer votes 2) Add Sankey Chart for displaying transfers 3) Allow for users to navigate between rounds to find the first-choice votes and transfers for each.
2
1
Hide tiny MKR votes by default
We're dealing with tons of tiny voters (<0.05 MKR) that are likely airdrop farmers. We should hide them from the UI using a toggle
1
·
planned
1
Explore improvements to governance metadata infra
Currently we rely on GitHub for hosting & managing governance metadata (eg. delegate details, poll metadata, exec markdown). Look into ways to make more efficient use of this platform, look into performance gains of moving the metadata to the same repo as the GovPortal, look into alternatives for GitHub. Optimise for security (granular access control) and performance.
3
·
under review
1
'Add to calendar' feature for governance polls
Allow users to generate a calendar event for poll expiry
0
0
Integrate "withdraw MKR from chief" into delegate contract creation flow
screenshot shows it's not prominent enough. imo withdrawing from chief and delegating it to ones own delegation contract should be a built-in step of delegate contract creation. We should either 1) make it part of the mandatory flow for delegate contract creation or 2) make it more visually prominent Adam suggested we batch these actions together in one tx. Should be a checkbox option though, and not necessarily required or done automatically Would need a design
0
1
Maker Governance Alert feature
Goal Increase the visibility/awareness of potentially dangerous scenarios related to the state of Maker governance through providing automated warning messages in the UI. Context This idea was birthed when recently someone spotted a large sum of MKR being borrowed on Aave. Such on-chain events (eg. large deltas in MKR lending market liquidity) currently are not easy to spot and rely on individuals blowing the horn. We should explore ways to automatically provide warnings/visual cues when such dangerous scenarios occur. Initial ideas in the comments below. To-do Brainstorm states and events that should trigger warnings Determine warning types (ie. banner messages) Explore designs Work breakdown + implement
2
1
DssSpell breakdown feature
Goal Upgrade the Spell detail tab to prepare for some upcoming changes to how CUs collaborate on spells and how spells impact the Maker system Context There are two major changes coming up to how spells are created and used in the Maker ecosystem: A) PE will no longer be the only team to create spells—CES will join them and more CUs will in the future. B) Once Maker Wormhole has reached some milestones and MCD is available on an L2 (or more), we will have multi-chain spells. This means that a spell may contain parameter changes across various chains. The above creates the following needs/requirements: 1) We need an interface for Core Units to collaborate on spell creation. 2) We need to show transparency on which param changes were added by which CU 3) We need to expand/improve the on-chain effects feature so that it can differentiate between param changes across various chains in the UI. ### To-Do 1) @0xdeniz to make initial sketches 2) @0xdeniz to iterate on sketches with @tiagovarandas8666 in Colorado 3) Iterate on sketches with Wouter in Colorado 4) Validate ideas with CES and PE 5) Create designs 6) Work breakdown 7) Plan for Q2 8) Implement
1
0
Load More
→
Powered by Canny