.///. .///. //. .// `/////////////-
`++:++` .++:++` :++` `++: `++:......---.`
`/+: -+/` `++- :+/` /+/ `/+/ `++.
/+/ :+/ /+: /+/ `/+/ /+/` `++.
-::/++::` /+: -::/++::` `/+: `++: :++` `++/:::::::::.
-:+++::-` `/+: --++/---` `++- .++- -++. `++/:::::::::.
-++. .++- -++` .++. .++. .++- `++.
.++- -++. .++. -++. -++``++- `++.
`++: :++` .++- :++` :+//+: `++:----------`
-/: :/- -/: :/. ://: `/////////////-
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 in the Aave Governance
Install it and run:
cp .env.example .env.local
yarn
yarn dev
For instructions on local development, deployment, configurations & feature proposals, see Contributing
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 main IPFS hash with all networks enabled
- the DNS of https://app.aave.com will always point to the latest main 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
https://app-aave-com.<your gateway>
To all the Ethereum community