Skip to content

DAVI v2.2.0

Compare
Choose a tag to compare
@rossneilson rossneilson released this 12 Dec 13:47
· 154 commits to master since this release
72e9539

DAVI Release v2.2.0

https://projectdavi.eth.limo/

This release of DAVI has again been autonomously executed via a guild on DAVI with controller ownership over the ENS name.

At the beginning of the new year we will kicking off DXdao’s new budget structure with DXdao teams using DAVI for daily operations. You can read the budget proposals in the forum and we are looking forward to dogfooding DAVI!

https://daotalk.org/t/phase-3-dxdao-budgetary-process-v1/4711

This release sees a major performance improvement in how DAVI works and fetches data. Previously we used polling for new data which hit both our RPC providers and user machines very hard. Now we are listening for events

The week before this change we saw daily relay’s by pokt in the millions and now we are down to a daily average of just a few thousand relays. The CPU usage graphs are also below (not entirely scientific benchmark, but a clear improvement). This comes at a great time before we scale our users up to the entirety of DXdao.

Before

https://user-images.githubusercontent.com/75996796/205053634-d6e0ed90-f22d-4f5a-ad37-43c68bbf11fc.png

After

https://user-images.githubusercontent.com/75996796/205053580-be1ed17a-a4ad-45eb-a8eb-91600e3f21b5.png

Changelog

  • 🚀 Added approve call to asset transfer permissions

  • 🔧 Replaced watch flags for event listeners - Huge performance improvements

  • 🔧 Upgraded wagmi library to 0.7.15

  • 🐛 Fixed "X" incorrectly showing on some NumericalInput components

  • 🐛 Fixed error display on setGuildConfig

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.

Coming up in the next release