---
# System prepended metadata

title: Endgame Frontend blockers

---

# Endgame Frontend blockers

## Secure MetaDAO "business frontend" white label skeleton

This codebase or specification must enable each MetaDAO team to easily copy paste and deploy to a website or downloadable file. 

The most important thing is that we define how to securely implement the most crucial use cases that the MetaDAOs will rely on to generate their base revenue, enable access to MetaDAO yield farming as well as the core requirement for MetaDAOs to provide access to MKR delegation and yield farming

### Dai yield farming

This is a simple UI element that allows a user to deposit Dai, and choose a MetaDAO token to farm in return. The UI then sends a transaction to transfer the Dai to the relevant MetaDAO token farm

### ETHD Vault (yield farming)

This is a UI element that at its basic gives access to the standard ETHD Vault type that enables MetaDAO yield farming. The user specifies 3 things:
* Amount of ETHD to deposit
* Amount of Dai to generate
* Which MetaDAO token to farm
A transaction is then generated to open the vault and deposit it to the relevant farm

### stETH to ETHD conversion

This is a dependency for the above feature. A simple 1:1 swap button that allows users to convert back and forth between stETH and ETHD. 


Non blocking future improvements:
* Improved to also exchange ETH to stETH and then ETHD
* Even better is to directly integrate this feature with the vault creation above

### MKR delegation, vault and MetaDAO yield farming

An advanced UI element that enables a user to go through a flow of:
1. Choosing amount of MKR to farm with 
2. choosing a delegate and a DVC strategy with information available about the top DVCs --- the easy delegation frontend
3. Choosing which MetaDAO to yield farm
4. (optional) choose to generate Dai

### Easy delegation frontend

The easy delegation frontend is meant to reduce the superficial complexity of making a decision about governnace to choosing a representative and a DVC that expresses the MKR holders view.

It has a sidebar or some other prominent information pane that ranks the DVCs and explains clearly their overall views: e.g. growth vs surplus vs resilience

on the same page, recognized delegates are randomized and available, with their DVC affiliation clearly shown. The user cannot delegate directly to a DVC, but must choose which delegate they want. This is to ensure that delegates can be a check on DVCs going rogue or breaking down.

Users can click through to more detailed delegate pages, but the delegates themselves can at most have a few keywords.

The main risk is that the user is overloaded and doesnt bother to make a decision, and instead just clicks randomly to move on and start farming. 

### MetaDAO and DVC forums

The MetaDAOs must have easy access to their centralized forums from their metadao frontend

Recognized DVC forums must also be available and accessible from the easy delegation frontend