DAOCensus

DAOs are becoming more and more popular, and are lacking tools to manage their dApps and community. Some key features are missing such as updating the frontend or backend of dApps. Most dApps are for the moment hosted in a centralized way, and managed by a small number of admins. These issues go against the main concepts of DAOs, and are limiting their development.

That's why we built an architecture to decentralize the process of dApps frontend updates. To do so, we're decentralizing the frontend hosting. Moreover, we designed an architecture to enforce each update to be approved by the majority of the DAO stakeholders. We also developed a browser extension, whose job is to check that the version of the visited website has been approved by the DAO before allowing the user to view it.

Concerning our architecture, anyone can make an update proposal after authenticating on Worldcoin to avoid spams. Then the new version proposed will be deployed dencentrally on IPFS and accessed using an ENS address. A vote will be made on snapshot for DAO token holders to decide if the update should be accepted. This vote is then verified on-chain using an optimistic oracle made on UMA. Any one can challenge this vote if they can prove that it hasn't been accepted by the snapshot vote. If the vote passes, the new version hash will be stored in this oracle and labeled as "whitelisted", then deployed by the DAO.

Finally, the users visiting the website will be alerted if the frontend he's on isn't listed in the oracle as whitelisted, using the browser extension we developed.

As only the IPFS hashes are stored in the on-chain whitelist, our architecture allows any user to deploy one of the validated versions on their own ENS domain, in case the DAO admins are not updating the frontend on fleek. That way, the frontend update process becomes decentralized and censorship resistant.