Add renFIL support to Aave
01Summary
Add renFIL (Ren Protocol's wrapped Filecoin) as a deposit and borrowing asset on Aave, but not as collateral. renFIL will use ChainLink price feeds and have conservative risk parameters including a 35% reserve factor and high interest rate slopes to manage counterparty and market risks.
- Type
- protocol addition
Key changes
- Enable renFIL deposits and borrowing (not collateral) on Aave market(high)
- Set LTV, liquidation threshold, and liquidation bonus to 0 to prevent use as collateral(high)
- Configure variable interest rate model with 80% optimal utilization, 7% slope1, and 300% slope2(high)
- Set reserve factor to 35% to manage counterparty risks(medium)
- Disable stable rate borrowing for renFIL(medium)
- Deploy four new smart contracts: aRENFIL token, variable debt token, stable debt token, and strategy implementation(medium)
Notable concerns
- RenFIL has centralized counterparty risk with proxy admin and EOA that can mint, burn, and change exchange rates
- RenFIL has very limited market liquidity and unknown market capitalization
- RenFIL assigned Risk Rating C for smart contract and counterparty risks
- Ren Protocol uses multisig with only 7-day timelock for contract upgrades, which may be insufficient to mitigate consequences
- EOA has unilateral ability to burn tokens potentially affecting aToken holders
- RenFIL collateral support explicitly not enabled due to price instability concerns
Generated by Kvorum
02Description
Simple Summary
Add depositing and borrowing (not collateral) support for renFIL to the Aave market. renFIL is a wrapped version of Filecoin using Ren Protocol.
Abstract
Filecoin brings decentralized storage to DeFi, and renFIL allows all types of new decentralized applications to be built to further the space. But these applications need a robust lending market to thrive, so storage miners can borrow renFIL/FIL to stake and FIL holders can earn a return on their holdings.
This proposal describes adding depositing and borrowing (not collateral) support for renFIL to the Aave market to unlock these new applications, expose the Filecoin community to Aave, and create a large new market on the protocol. Ren Protocol was chosen as the tokenization service because it is already managing large bridges in production, including $301 million in renBTC as of this writing. Collateral support for renFIL may be added later, but we recommend waiting for more price stability of FIL and renFIL before enabling.
Motivation
Filecoin, and by extension, renFIL is unlike any other digital asset currently available in the Aave market, as it allows the purchase of hosting space on the permissionless Filecoin network. As a result, being able to lend and borrow renFIL will unlock many new DeFi applications, including:
- Storage mining syndicates
- Data markets
- Shared UIs/images/content
- Lossless capital hosting
Just see the recent EthGlobal<>Protocol Labs Hackathon and Filecoin Launchpadfor hints of what is possible at the intersection of Filecoin+DeFi. The Filecoin community is massive and growing everyday, however, many of the participants are unfamiliar with Aave and DeFi. Adding renFIL to Aave would dramatically increase support for these efforts, would bring Filecoin users/developers into the Aave ecosystem, and allow capital, yield, and value to accrue to Aave participants.
Specification
Project
Filecoin is a distributed storage network based on a blockchain mechanism. Filecoin miners can elect to provide storage capacity for the network, and thereby earn units of the Filecoin cryptocurrency (FIL) by periodically producing cryptographic proofs that certify that they are providing the capacity specified. In addition, Filecoin enables parties to exchange FIL currency through transactions recorded in a shared ledger on the Filecoin blockchain. Rather than using Nakamoto-style proof of work to maintain consensus on the chain, however, Filecoin uses proof of storage itself: a miner’s power in the consensus protocol is proportional to the amount of storage it provides.
Filecoin was founded in 2015 by Juan Benet, has been backed by Sequoia Capital, Andreessen Horowitz, and Union Square Ventures, and its mainnet went live on October 15, 2020. The network is governed by the Filecoin Foundation and the Filecoin Foundation for Decentralised Web.
Rationale
The REN token is already supported in the Aave market, and renBTC is one of the most popular cross-chain tokens today. In unifying the Filecoin and DeFi ecosystems, Ren protocol is a natural bridge and has the technical expertise and experience to get the job down securely and safely.
Implementation
The Filecoin price oracle will be served via ChainLink, which includes both FIL/ETH and FIL/USD feeds.
The renFIL token will only be used for depositing and lending, not as collateral. The following strategy params are proposed:
IReserveParams = {
optimalUtilizationRate: new BigNumber(0.8).multipliedBy(oneRay).toFixed(),
baseVariableBorrowRate: '0',
variableRateSlope1: new BigNumber(0.07).multipliedBy(oneRay).toFixed(),
variableRateSlope2: new BigNumber(3).multipliedBy(oneRay).toFixed(),
stableRateSlope1: '0',
stableRateSlope2: '0',
baseLTVAsCollateral: '0',
liquidationThreshold: '0',
liquidationBonus: '0',
borrowingEnabled: true,
stableBorrowRateEnabled: false,
reserveDecimals: '18',
aTokenImpl: eContractid.AToken,
reserveFactor: '3500'
};
Following the steps from the Aave governance docs, the following contracts were generated:
New interest bearing asset deployed on main:
Interest bearing aRENFIL address: 0x5CAF29fD8efbe4ED0cfc43A8a211B276E9889583
Variable Debt variableDebtRENFIL address: 0x4B20f007d0c1567Ca8a6e80B8a8EE19Ac59C6a08
Stable Debt stableDebtRENFIL address: 0xf22b80D58a7cCDEd772E0997AE90a6C77940B051
Strategy Implementation for RENFIL address: 0xb140cb1306B396c658A5438602b6857842E1E98a
Test Cases
Audits/Security Reviews
Ren Protocol audits from ChainSecurity, ConsenSys Diligence, and Trail of Bits
Filecoin audits and bug bounty
AAVE Community renFIL Risk Assement

RenVM is a byzantine fault-tolerant network that is able to securely in a decentralized manner do ECDSA threshold key generation and signing via sMPC, which allows RenVM to securely manage private keys of different assets like Bitcoin and Filecoin, and wrap these assets on smart-contract chains. Since launch, RenVM has processed around $1.5B in total volume of Bitcoin, Filecoin, Zcash, Bitcoin cash going to and from Ethereum. The smart contract risks of RenFIL are mitigated by those of RenBTC which has been battle tested by the markets.
Technically, renFIL is a proxied token standard ERC with some features on top:
- Mechanism of exchange rate (similar to Aave slashing)
- Permit for approvals
- Recovery of other tokens sent to the contract
RenFIL Counterparty Risk: C
There is a proxy admin which can update all the logic of the contract with a 7 days timelock controller by a multisig, controlled by the team. Even with 7 days, it may be impossible to mitigate the consequences of a contract upgrade with minting for example.
Furthermore there is an EOA (Externally Owned Account) with permissions to mint, burn, change the exchange rate and decide which tokens sent by mistake to the renFIL contract are recoverable.
This results in the capability to burn tokens of a particular address (potentially the ones contained in aToken) and the change of the implementation under the proxy.
RenFIL Market 1: Risk B (based on FIL)
RenFIL market capitalisation is unknown with very little liquidity in the markets. The redemption process is permissionless enabling smooth liquidations into the liquidity of FIL.
Risk Parameters
Given the centralisation of RenFIL it can only be listed as borrow asset.
Reserve Factor 35%
Variable Interest Rate Model
UOptimal 80% (since not a collateral)
R_0 0%
R_s1 7%
R_s2 300%

References
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
A calldata-vs-description analysis is not generated yet. Review the decoded actions →
04Actions
- Target
- 0xe775…4473
- Value
- 0 wei
- Function
- execute(address,address,address,address,address,uint256,uint256,uint256,uint256,uint8,bool,bool,bool)
- Arguments
{ "0": "0xD5147bc8e386d91Cc5DBE72099DAC6C9b99276F5", "1": "0x5CAF29fD8efbe4ED0cfc43A8a211B276E9889583", "2": "0xf22b80D58a7cCDEd772E0997AE90a6C77940B051", "3": "0x4B20f007d0c1567Ca8a6e80B8a8EE19Ac59C6a08", "4": "0xb140cb1306B396c658A5438602b6857842E1E98a", "5": "0", "6": "0", "7": "0", "8": "3500", "9": "18", "10": false, "11": false, "12": false }- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| DD0xdd70…8202 | For | 183.6K | 51.73% | — | 6y ago |
| 9B0x9b5e…0499 | For | 100.7K | 28.36% | — | 6y ago |
| 700x704d…a0df | For | 27K | 7.62% | — | 6y ago |
| 800x80dc…c146 | Against | 19.2K | 5.42% | — | 6y ago |
| 470x47c1…4770 | For | 8.3K | 2.32% | — | 6y ago |
| E00xe05f…54aa | For | 8.2K | 2.30% | — | 6y ago |
| 970x9757…e331 | For | 4K | 1.13% | — | 6y ago |
| AC0xaccf…303a | For | 1.3K | 0.37% | — | 6y ago |
| CA0xca76…6f46 | Against | 525 | 0.15% | — | 6y ago |
| EA0xea4e…2384 | For | 315.7 | 0.09% | — | 6y ago |
| A70xa7dc…3d0f | Against | 240.2 | 0.07% | — | 6y ago |
| 110x1169…0393 | Against | 211.1 | 0.06% | — | 6y ago |
| F40xf4f5…52ea | For | 181.1 | 0.05% | — | 6y ago |
| 4F0x4f2f…f22b | For | 162.6 | 0.05% | — | 6y ago |
| CF0xcfa6…e428 | For | 133.8 | 0.04% | — | 6y ago |
| B70xb7f6…5544 | For | 119.8 | 0.03% | — | 6y ago |
| 600x6001…887a | For | 108.1 | 0.03% | — | 6y ago |
| F70xf72a…e97c | For | 100 | 0.03% | — | 6y ago |
| 560x5674…9b7c | For | 100 | 0.03% | — | 6y ago |
| 280x2875…63e9 | For | 84.7 | 0.02% | — | 6y ago |
| 7F0x7f18…caed | Against | 70.6 | 0.02% | — | 6y ago |
| CF0xcf88…b88c | For | 51.2 | 0.01% | — | 6y ago |
| 8D0x8d07…a265 | For | 50 | 0.01% | — | 6y ago |
| C90xc91a…a7c8 | For | 30.2 | 0.01% | — | 6y ago |
| 370x37fa…e7a0 | For | 27.9 | 0.01% | — | 6y ago |
| 430x43b3…b9b0 | For | 25.4 | 0.01% | — | 6y ago |
| E50xe58d…1c31 | Against | 24 | 0.01% | — | 6y ago |
| B50xb50b…f632 | Against | 23 | 0.01% | — | 6y ago |
| 270x274a…3b3b | For | 13.1 | 0.00% | — | 6y ago |
| 550x550a…54e0 | For | 9.1 | 0.00% | — | 6y ago |
| BB0xbb95…6e87 | For | 8.5 | 0.00% | — | 6y ago |
| 100x10d6…7178 | For | 6.4 | 0.00% | — | 6y ago |
| 800x80f1…0cfa | For | 3 | 0.00% | — | 6y ago |
| C50xc54a…4592 | For | 2.7 | 0.00% | — | 6y ago |
| 7E0x7ecb…95ed | For | 2.5 | 0.00% | — | 6y ago |
| 490x4908…59b9 | Against | 2 | 0.00% | — | 6y ago |
| 300x3070…ec29 | For | 2 | 0.00% | — | 6y ago |
| D80xd832…8d35 | For | 1.1 | 0.00% | — | 6y ago |
| 500x506c…419d | For | 1 | 0.00% | — | 6y ago |
| 400x400a…f934 | For | 1 | 0.00% | — | 6y ago |
| 1E0x1e0d…d676 | For | 1 | 0.00% | — | 6y ago |
| 900x908e…b08f | For | 0.7 | 0.00% | — | 6y ago |
| 630x632c…a82b | For | 0.7 | 0.00% | — | 6y ago |
| 550x5564…8ebc | For | 0.7 | 0.00% | — | 6y ago |
| 320x3257…885d | For | 0.7 | 0.00% | — | 6y ago |
| 290x2961…a763 | For | 0.7 | 0.00% | — | 6y ago |
| 070x073d…22c2 | For | 0.7 | 0.00% | — | 6y ago |
| 980x98e6…8d49 | For | 0.7 | 0.00% | — | 6y ago |
| 8E0x8ed4…c063 | For | 0.7 | 0.00% | — | 6y ago |
| 220x22f9…c329 | For | 0.7 | 0.00% | — | 6y ago |
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
- aaveexecutedUpdate renFIL rate strategy on Aave v2 Ethereum80%
- aaveexecutedAdding AMPL on AAVE66%
- aaveexpiredConsolidate Reserve Factors and Enable Borrowing DPI65%
- aaveexecutedConsolidate Reserve Factors and Enable Borrowing DPI65%
- aaveexecutedAdding BAL on AAVE63%
- aavedefeatedAdd BarnBridge (BOND) to Aave62%
- aaveexecutedLower Reserve Factor for AMPL61%
- aaveexecutedUpgrade AMPL implementation59%
- aaveexecutedRaise Maximum Interest Rate on AMPL Market59%
- aaveexecutedCRV Interest Rate Curve Upgrade58%