.///.                .///.     //.            .//  `/////////////-
       `++:++`              .++:++`    :++`          `++:  `++:......---.`
      `/+: -+/`            `++- :+/`    /+/         `/+/   `++.
      /+/   :+/            /+:   /+/    `/+/        /+/`   `++.
  -::/++::`  /+:       -::/++::` `/+:    `++:      :++`    `++/:::::::::.
  -:+++::-`  `/+:      --++/---`  `++-    .++-    -++.     `++/:::::::::.
   -++.       .++-      -++`       .++.    .++.  .++-      `++.
  .++-         -++.    .++.         -++.    -++``++-       `++.
 `++:           :++`  .++-           :++`    :+//+:        `++:----------`
 -/:             :/-  -/:             :/.     ://:         `/////////////-

This repository is deprecated, and deployment has been moved to classic.aave.com and will not be maintained any longer.

The new Aave app client repository can be found here and the app can be accessed here.

An open source interface for the decentralized liquidity protocol Aave

Enabling users to:

• Manage and monitor their positions on the Aave Protocol, and the overall status of it
• Manage and monitor their positions on the Aave Safety module
• Participate on the Aave Governance

Each commit gets deployed to IPFS automatically

There's a github action commenting the appropriate IPFS hash embedded in the Cloudflare IPFS gateway after each commit

For ease of use:

• the DNS of https://staging.aave.com will always point to the latest master IPFS hash with all networks enabled
• the DNS of https://app.aave.com will always point to the latest master IPFS hash with disabled test networks

Issue: I cannot connect to app.aave.com

The aave-ui is hosted on IPFS in a decentralized manner. app.aave.com just holds a CNAME record to the Cloudflare IPFS gateway. You can use any public or private IPFS gateway supporting origin isolation to access aave-ui if for some reason the Cloudflare gateway doesn't work for you

Just go to <your favorite public ipfs gateway>/ipns/app.aave.com

⚠️ Make sure the gateway supports origin isolation to avoid possible security issues: you should be redirected to URL that looks like https://app-aave-com.<your gateway>

• https://app-aave-com.ipns.cf-ipfs.com/#/
• https://app-aave-com.ipns.dweb.link/#/

For instructions on local development, deployment and configurations, see Contributing

For instructions on verifying the contract addresses you are interacting with, see Verification

BSD-3-Clause

To all the Ethereum community