The network/protocol is decentralized but we have to go through an aave.com interface, what happens if the site is down for x or y reason? We can certainly use smart contract but who is able to do it without interface / frontend?
We can use zapper, instadapp, defisaver and others but we depend on their smart contract and protocol too.
Why not set up a public frontend? Which can be different from aave.com (lighter version) but which allows to interact with everything that is possible to do today on aave.com and on smartcontract?
Moreover if the frontend is public and decentralized, it is possible to add the latest features that are available on the protocol more quickly.
Other advantages : We will have the possibility to create mirrors
Risk : Possibility that someone change the addresses of the smart contract in the frontend if they decide to fork it and make a fake.
In any case I want to open the discussion on this eventuality and take the measure.
Moreover an Aave app seems to be in dev, is it public ? decentralized ? where is the border ?
If the protocol is decentralized, the interface must be too, otherwise we are dependent (for a large part of the users) on the goodwill of the person responsible for the publication of the frontend.
Of course all the frontend work is fabulous, but so far we are waiting for the new releases with impatience and we have no choice on the frontend, the date, etc …
- For a decentralized Aave frontend soon
- No decentralized Aave frontend at least for the moment