Enable borrowing on renFIL
01Summary
AIP finalizes renFIL (wrapped Filecoin) integration on Aave by enabling borrowing of the asset. This follows AIP-13 which was passed in April and allowed deposits but not borrowing. The proposal calls enableBorrowingOnReserve on the lending pool configurator to activate borrowing functionality for renFIL without stable rate borrowing.
- Type
- protocol addition
Key changes
- Enable borrowing on renFIL (wrapped Filecoin token)(high)
- Disable stable rate borrowing for renFIL(medium)
Generated by Kvorum
02Description
Simple Summary
AIP-13 added a wrapped version of Filecoin (renFIL) to Aave, and this AIP will finalize it by enabling borrowing of the asset.
AIP rationale
Over the past 6 months, AIP-13 has been proposed, debated, and ultimately passed on April 19th to allow deposits and borrowing (but not collateral use) on renFIL, a wrapped Filecoin token using Ren protocol. The discussion and trade-offs can be found on the governance forum here.
This AIP finalizes the previous submission to configure the renFIL asset as a borrowable currency on Aave.
Implementations details
The proposal will:
- Enable borrowing on renFIL
- Target the lendingPoolConfigurator: https://etherscan.io/address/0x311bb771e4f8952e6da169b425e7e92d6ac45756
- Call its enableBorrowingOnReserve(asset, enableStableBorrow) with argument (0xD5147bc8e386d91Cc5DBE72099DAC6C9b99276F5, false)
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The description explicitly states the single action to be taken: calling enableBorrowingOnReserve on the lendingPoolConfigurator contract with the renFIL asset address and stable borrow disabled (false). The decoded calldata contains exactly one action matching this function signature, target address, and arguments (asset address and boolean flag match exactly). There are no additional actions in the calldata beyond what is described, no value transfers, and no discrepancies in target address, function name, or parameters. This is a straightforward, single-action proposal where the prose and calldata align perfectly.
Generated by Kvorum
04Actions
- Target
- 0x311b…5756
- Value
- 0 wei
- Function
- enableBorrowingOnReserve(address,bool)
- Arguments
{ "asset": "0xD5147bc8e386d91Cc5DBE72099DAC6C9b99276F5", "stableRateEnabled": false }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- Proposal: add support for renFIL (Filecoin) ↗discourse · high confidence
Arguments for
- Adding renFIL unlocks new DeFi use cases for decentralized storage, benefiting the Filecoin and Aave ecosystems.— corbpage, MaxRoszko, mitche50, protocolin
- The proposal is a win-win-win, generating new TVL and fee revenue for Filecoin, Ren, and Aave simultaneously.— Sunshine, Christael, S_rank
- Borrowing renFIL lets storage miners bootstrap or scale mining operations without needing to first buy FIL or hardware outright.— MarcZeller, nicola, clouds, defifrog
- FIL holders and large investors could use FIL as collateral to diversify or lend to miners for yield, creating new financial strategies.— MarcZeller, nicola
- Ren Protocol is a proven, battle-tested bridge technology (e.g. renBTC) which mitigates smart contract risk for renFIL.— corbpage, Alex_BertoG
- A conservative, phased approach—enabling borrowing first and collateral later with cautious risk parameters—reduces risk given FIL's price volatility.— Sunshine, MarcZeller, corbpage
- Competing platforms (Cream, MakerDAO) are also moving toward listing FIL-wrapped assets, suggesting Aave should keep pace.— nicola, MaxRoszko
Arguments against
None surfaced.
Unresolved concerns
- RenFIL has significant centralization risk: a proxy admin and EOA can mint, burn, or change the exchange rate, potentially harming aToken holders even within the 7-day timelock.— Alex_BertoG
- RenFIL's market capitalization is unknown and liquidity is very limited, raising concerns about smooth liquidations.— Alex_BertoG
- There is no consensus on whether renFIL is the best wrapped FIL option compared to alternatives like WFIL or HFIL.— nicola
- It remains unconfirmed whether Ren's library (renJS) can enable direct conversion and transfer of borrowed renFIL into native FIL wallets for miners.— defifrog
- The on-chain governance vote struggled to reach quorum, requiring delegation and last-minute voter mobilization.— MaxRoszko, corbpage
Notable participants
- corbpageProposer from ConsenSys Codefi who introduced and championed the renFIL borrowing proposal and later pushed for votes to meet quorum.
- MarcZellerEarly strong supporter who detailed use cases for miners and collateral users and advocated for conservative risk parameters.
- nicolaProvided detailed breakdown of user categories (storage users, miners, investors) and tracked competitive landscape across other protocols.
- Alex_BertoGAuthored the formal risk analysis covering smart contract, counterparty, and market risk, recommending borrow-only listing with specific parameters.
- MaxRoszkoFrequent supportive commenter who also helped organize delegation and voter turnout for the on-chain proposal.
- defifrogRaised a technical question about renJS's capability to enable native FIL borrowing/conversion.
- cloudsSupported the proposal while raising a clarifying question about how renX tokens would be represented in Aave.
- SunshineExpressed strong support emphasizing the phased, risk-reducing rollout approach.
Generated by Kvorum
08Similar proposals
- aaveexecutedRe-enable ETH Borrowing69%
- aaveexecutedPause ETH Borrowing68%
- aaveexecutedRisk Parameter Updates for Aave v2 Ethereum Liquidty Pool67%
- aavecanceleddesactivation of Aave V1 stable rate borrowing65%
- aaveexecutedPause LINK Borrowing65%
- aaveexecuteddesactivation of Aave V1 stable rate borrowing65%
- aaveexecutedPause UNI Borrowing64%
- aaveexecutedDisable Stable Borrows64%
- aaveexecutedDisable borrow for xSUSHI and DPI. Freeze reserves for UNI and BAL AMM Markets63%
- aaveexecutedRisk Parameter Updates for Aave V2 ETH Market (2022-11-12)61%