This is a proposal to turn DxDAO’s Alchemy into a Dwebsite (=decentralized website) that uses only ENS and IPFS.
I’m from Almonit organization for Dwebsites, where we see such steps as essential in having true decentralized Dapps and DAOs. This is testing the water proposal, we’d like to hear your opinion about this idea before submitting it for DXdao to vote on.
DXdao members use Alchemy to interact directly with the DAO. Most do it via
alchemy.daostack.io, though in principle “power users” can also create their own Alchemy instance on a different server (or locally on their computer).
There are two centralization and security problems with how Alchemy is used right now.
The first is for users of
alchemy.daostack.io. The problem is that
alchemy.daostack.io is centralized, so if attackers gain access to it, they can manipulate DXdao members by presenting false information. This problem doesn’t exist for people who run Alchemy locally, but those are a small minority.
The second problem is that Alchemy uses the services of The Graph to get structured data from Ethereum. For our knowledge this was done for UX reasons, but there is a possibility to replace it with direct data from Ethereum blockchain (using a web3 provider or a local node). This problem exists for all users of Alchemy, even those who run an instance of it locally.
(theoretically, it is also possible for users to maintain their own service of The Graph, but this again requires resources and technical knowledge that most don’t have.)
We propose to turn Alchemy into a Dwebsite running on ENS + IPFS. This will decentralized the DXdao interface, so that members could use DXdao in a decentralized private way.
This is possible since Alchemy is built as a standalone Webapp. There are three steps in creating this solution.
Connecting DXdao to an ENS name (we’re not sure yet which name, possibly alchemy.dxdao.eth). The idea is that DXdao decisions regarding Alchemy Dwebsite will automatically update the Dwebsite. We need to create smart contracts to create this connection.
Changing routing in Alchemy to make it an IPFS website. this step is purely technical. The paths in Alchemy, as it is built today, need to be changed in order to run it on IPFS.
(optional) Substituting dependency on The Graph by directly querying Ethereum blockchain. We’re not sure if this step is desired by the community. also, it may turn out to be quite a lot of work.
Currently we’re thinking of making a proposal for steps 1+2, which are necessary steps for an Alchemy Dwebsite. Later on we could extend it with another proposal for step 3.
Almonit (or: who are we to make this offer?)
Almonit is an internet project for Dwebsites. We started as a side-project of a few friends in the second half of 2019. Our goal is to decentralized the web, especially by checking the limits of what can be done with Dwebsites. In the process we’d like to bootstrap as many projects as possible, such as DXdao, into the Dwebsites sphere.
Under this umbrella we released two things so far.
Browser extension for accessing Dwebsites: Firefox (recommended) and Chromium-based browsers.
Decentralized search engine for Dwebsites: almonit.eth (or almonit.eth.link if you don’t have a browser extension to access .eth websites directly).
As part of making the search engine we also took upon ourselves the curate the Dwebsites world, so we know that DXdao already got a Dwebsite of its own: dxdao.eth.
We are in touch with DAOStack people. This proposal stemmed out of discussions with them.
We didn’t discussed costs and time-frame yet because we want to see first the community thinks. So please, let us hear your thoughts!