DAVI v2.0.1 - Public beta
Public beta
A few weeks ago we opened DAVI up in private beta for internal testing in DXdao and to get it into people’s hands alongside a demo. The private beta was defined as still being on testnets like Goerli. But now we have deployed to production networks we are entering public beta.
The main audience is still very much DXdao as we need to dogfood guilds internally before onboarding external organisations onto DAVI.
The public beta consists of our initial guilds launching on Mainnet and gnosis chain (maybe Arbitrum soon too):
- ERC20 guilds - The guilds are built around an existing ERC20 token requiring users to lock the token for voting power.
- SWPR guild - Coming soon 👀
- DXD guild - In production now as we test inter-DAO voting. Please do not lock DXD yet, we will announce separately when it is ready with the initial 4% voting power in DXdao.
- REP guilds - These operate around a reputation token the same as DXdao and will be used to facilitate DXdao actions usually undertaken by a MS. It can also provide a scalable solution to communities or teams just starting operations.
You may also notice our guilds have the same addresses across chains now thanks to some upgrades to our deployment processes.
And if you take a look at the Mainnet guild’s past proposals you’ll even see that we used DAVI to launch DAVI via ENS updates!
We’ll see if we can find some time to demo DAVI’s public beta to everyone soon also.
Changelog
Compared to the previous version, 1.2.0, most of the changes have been under the hood and bug fixes.
- Updated readability of contracts
- Improved how we read guild types with added caching
- Added Mainnet and gnosis chain registries
- Support CID v1 in ENS update action
We need you
The whole logic behind the ecosystem vision of DXdao’s products enabling community freedom is that DXdao will be the first to use all of these products and is building them because it sees a need. This should encourage others to see DXdao doing cool things and want to emulate us. So in order to show others everything guilds can do inside DAVI we need to use them ourselves.
We will likely use the current Mainnet rep guild for paying out hackathon prizes in the next week. In addition of course DXD guild will soon be getting tested utilising it’s REP.
Beyond this, phase 2 of restructuring calls for each squad to have its own budget and OKRs which will require the squad having its own on chain entity, a perfect chance for guilds to shine.
DXgov will lead since we are well positioned both for goals and in experience with DAVI but shortly all squads should be using DAVI for their operations. We can also use discussions and social features inside those guilds to document efforts and discussions specific to each squad.
If you have any further ideas on how we can use DAVI internally please suggest them to the DXgov team!
We also need to add contracts to our config, if you know a contract you want a DAVI DAO to be able to call then let us know!
Longer term we have some potential partners and DXgov’s next priority is supporting Gov 1.5 and migrating DXdao to DAVI.
Providing feedback
To collect feedback we have set up canny:
https://davi.canny.io/features
For larger feature requests or suggestions please write them here. Also, feel free to vote on existing features that you would like to see. All of this will help us build DAVI into a better product.
For bug reports or general feedback you can also write them down in a google doc and send them to the DXgov team, they will then be aggregated into one notion document. Updates will then be provided by comments in this document. The more screenshots and descriptions you give the better.
https://rossneilson.notion.site/Feedback-v2-0-1-f2cd1bd645a847e9a9d5a5c4b102f2f9
Coming up in the next release
- Action builder 🏗️
- Support for factory-style contracts in action builder 🏗️
- Default values in action builder
- ENS name support for address inputs
- Raw transaction builder
- Improved permission setting and checking
- Social MVP 👀