Features

With DAVI we have a pretty amazing opportunity for DAOs to build and structure their org how they wish. This could be a main DAO with wallet schemes providing specific functionality and even connected teams of guilds with their own budgets and responsibilities. Mapping this all out would give an until now non existant overview of how an organisation is structured.

Our ERC20 guilds have a token vault for storing the ERC20 tokens for power in the guild. This could be transferred quite easily over to an NFTVault to allow us to support NFT Guilds. We would have to track the exact NFT locked for each user and some interfaces around this would be needed but otherwise, it would be fairly simple. Likely requires at least a small audit.

A deployment wizard for any user to quickly spin up a new gov 2.0 DAO with the exact requirements and customisation or template selection they want with no technical knowledge needed. How we handle maintaining the same address across networks may be tough but we can also have some centralisation here with a serverless function since it is not require to make DAVI operate (DAOs can always be deployed manually with scripts in github)

This UI / UX challenge aims to design an interface which can show all active proposals from all DAOs There should be a few ways of sorting this list of proposals, by proposals already getting voted on by, controversial proposals, and incentivised proposals. The interface needs to be clever about when it puts proposals on chain and what it directs users to do because timing is important when we are dealing with creating an on chain mirrored proposal to vote on another proposal. More work needs done on the exact strategy here. This feature will eventually lead to revenue for DAVI and DAOs built on DAVI. If it shows promise as a feature it could get its own contracts and more features like DAOs building proposals for other DAOs.

We have the ability to suport signed votes on the contract side of guilds and gov 2.0 but have yet to support it on the frontend, mostly because it is a slight UX challenge to support well. This would mean users could vote for free off chain with their signatures. We would collect these on orbis and then someone could aggregate them and upload them on chain with a single transaction. Some more experimentation would be required to find if there are any cost savings here but it is expected to still cost a similar amount. It is more like we are shifting the cost to one individual (perhaps we could automate this?) We will support this at some point since it is in the contracts but need to find out how much demand there is before prioritising it.