[ARC] - Integrate Unstoppable Domains login into the Aave app


Unstoppable Domains connects Web2 to Web3 through the use of blockchain domains. Using an Unstoppable Domain allows you to create a blockchain-connected web address similar to a URL — such as SomeName.crypto or SomeName.zil for example — that translates a cryptocurrency wallet’s addresses into a far simpler human-readable name that connects with dApps and exchanges.

Unstoppable Domains has over 2.5M domains registered, supports over 275 coins/tokens, and has over 450 integrations with other apps in its constantly growing ecosystem.

[Proposed integration]

In addition to providing users with human-readable wallet addresses, Unstoppable Domains also features an SSO-type decentralized universal Web3 login that can be integrated into any dApp.

The proposed integration would add Unstoppable Domains as an option to the wallet connect dialog of the Aave app.

Read more about Login with Unstoppable

[Current and proposed integration of Aave in the Unstoppable Domains ecosystem]

Due to Unstoppable Domains’ large and ever-growing user base, many current Aave users would likely already benefit from having this additional option to connect their wallet with the app. This number is bound to only go up in the future.

In addition, Unstoppable Domains can help more people find their way to Aave by listing the application on our website, as well as providing other co-marketing options, including but not limited to an announcement on our Twitter (280k followers), by resharing Aave posts/tweets, adding Aave as a partner on our main webpage, and adding information about Aave and our partnership to our newsletter (300k audience).

[Technical integration]

I have implemented the proposed integration in feat: login with unstoppable domains by leetdev · Pull Request #1041 · aave/interface · GitHub

1 Like

Update on this,

seems UD team posted a snapshot vote that will be open in ~24h


Github already has the PR work done, so if that proposal reaches quorum (100k YAE) and frontend team doesn’t detect safety issue and give greenlight it’ll be merged.


last update on this Topic,
this proposal was rejected by the snapshot vote with a majority of 172k NAY votes.

governance has spoken, closing this thread.