Author: ACI
Date: 2024-10-04
Simple Summary:
The current TEMP CHECK aims to onboard EIGEN, the native token of Eigenlayer, in Aave V3 Ethereum Market. This onboarding will allow Aave users to supply and borrow EIGEN, thereby enhancing the utility and liquidity of the Eigenlayer token within the DeFi ecosystem and more specifically, within the Aave ecosystem.
Motivation/Background:
Eigenlayer is a protocol focused on shared security and restaking, enabling Ethereum stakers to extend their security guarantees to multiple services and protocols. EIGEN is the governance and utility token for Eigenlayer, playing a critical role in the network’s operations, staking mechanisms, and protocol governance. By onboarding EIGEN to Aave V3, we aim to create new opportunities for Aave users to engage with this emerging staking ecosystem, while expanding EIGEN's liquidity.
Benefits of listing that token:
Provide opportunities for Aave users to borrow against their EIGEN to unlock liquidity, or alternatively to borrow EIGEN against other collateral allowing them to stake it in the Eigenlayer ecosystem to earn rewards.
Market Impact:
We see no significant market impact from onboarding EIGEN except for providing new opportunities to Aave users which may cause users to switch from borrowing other tokens against their collateral. Overall we see onboarding EIGEN as net good for Aave users as it expands opportunities for them to engage in a new, important ecosystem.
Chain to be deployed/listed:
Ethereum Mainnet
Proof of Liquidity (POL) and Deposit Commitments:
POL and Deposit Commitments will be discussed at the ARFC stage.
Useful Links:
Disclaimer:
This proposal is powered by Skywards. The Aave Chan Initiative is not directly affiliated with Eigenlayer Foundation and did not receive compensation for creation this proposal.
ACI and ACI employees may be holders of EIGEN.
Next Steps:
- If consensus is reached on this TEMP CHECK, escalate this proposal to the Snapshot stage.
- If the Snapshot outcome is YAE, escalate to ARFC stage.
- Publication of a standard ARFC, collect community & service providers feedback before escalating proposal to ARFC snapshot stage.
- If the ARFC snapshot outcome is YAE, publish an AIP vote for final confirmation and enforcement of the proposal.
Copyright:
Copyright and related rights waived under CC0
Off-Chain Vote
YAE
177.48K AAVE23.2%
NAE
1.44K AAVE0.2%
ABSTAIN
586.38K AAVE76.6%
Timeline
Oct 09, 2024Proposal created
Oct 10, 2024Proposal vote started
Oct 13, 2024Proposal vote ended
Feb 12, 2026Proposal updated