# \[ARFC\] Recognize HyperLend as a Friendly Fork **URL:** \ **Category:** Governance\ **Created:** [February 18, 2025, 8:06am UTC](https://governance.aave.com/t/arfc-recognize-hyperlend-as-a-friendly-fork/21129 "2025-02-18T08:06:27Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ACI](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/aci/32/4780_2.png) [@ACI](https://governance.aave.com/u/ACI)\ **Post date:** [February 18, 2025, 8:06am UTC](https://governance.aave.com/t/arfc-recognize-hyperlend-as-a-friendly-fork/21129/1 "2025-02-18T08:06:28Z")
## **[ARFC] Recognize HyperLend as a Friendly Fork** ## **Author: ACI** ## **Date: 2025-02-18** > Proposal updated to reflect latest changes on negotiations 2025-03-07 * * * ### Summary This proposal seeks to recognize [HyperLend](https://www.hyperlend.finance/) as a friendly fork of Aave, deployed on the Hyperliquid EVM chain (HyperEVM), after successful TEMP CHECK and TEMP CHECK Snapshot. ### Motivation HyperLend aims to support Aave’s ecosystem by sharing 10% of its protocol revenue with the Aave DAO and allocating 3.5% of its token supply to the DAO treasury. Additionally, 1% of the total supply will be airdropped to stAAVE holders, ensuring alignment with Aave’s community and stakeholders. ### About HyperLend: Beyond core multi-asset lending pools, we will have isolated pools to support riskier assets, and we are working with vault curators to create optimized yield strategies on top of our markets. Additionally, HyperLend will tokenize the HLP vault and perpetual positions, which will be available as collateral in the isolated pools. This will position HyperLend as the leading lending protocol on HyperEVM, driving liquidity and composability within the ecosystem. We are currently deployed on [HyperEVM testnet](https://testnet.hyperlend.finance/) (using MIT-licensed v3.0.2 codebase), with over 200k total users (10-20k daily, excluding known sybils). We are working with [Block Analitica](https://x.com/BlockAnalitica) as our risk manager, had additional audits done by [Ackee](https://ackee.xyz/), [Cantina](https://cantina.xyz/competitions/cd180bb3-5d7d-46ed-8b99-d905e54a9d0b), and [Pashov](https://www.pashov.net/), and have partnered with [Resolv](https://x.com/ResolvLabs), [Swell](https://x.com/swellnetworkio), [ThunderHead](https://x.com/ThunderheadLabs), [Stargate](https://x.com/StargateFinance), [RedStone](https://x.com/redstone_defi), [Pyth](https://x.com/PythNetwork), [Theo](https://x.com/TheoNetwork_) and more. By formally recognizing HyperLend as a friendly fork, Aave DAO can establish a mutually beneficial relationship with us, capturing additional value for the DAO and AAVE token holders, while allowing HyperLend to use its secure & battle-tested codebase. ### Specification We propose that HyperLend: - share 10% of the revenue (derived from the Aave codebase\*) with the Aave DAO (either distributed monthly or by using `RevenueSplitter` contract) - distribute 3.5% of the HyperLend (HPL) token supply to the Aave DAO (at TGE) - distribute 1% of the HPL token supply to stkAAVE holders (at TGE) - revenue from isolated pools, P2P, and non-lending aspects of the protocol (such as potential tHLP fees) is excluded In return, Aave DAO should: - Grant HyperLend the license to use the Aave codebase. In this sense, license to use the prior most recent release of Aave V3 (3.3) and any fix that could create functional or security issues with said version. - License will be limited to Hyperliquid EVM only. ## Disclaimer: This proposal is powered by Skywards. The ACI is not directly affiliated with Hyperlend and did not receive any compensation for creating this proposal. ## Next Steps 1. Publication of a standard ARFC, collect community & service providers feedback before escalating proposal to ARFC snapshot stage. 2. 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 via CC0. ---
**Author:** ![ACI](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/aci/32/4780_2.png) [@ACI](https://governance.aave.com/u/ACI)\ **Post date:** [March 10, 2025, 7:31am UTC](https://governance.aave.com/t/arfc-recognize-hyperlend-as-a-friendly-fork/21129/2 "2025-03-10T07:31:58Z")
The current proposal has been escalated to [ARFC Snapshot](https://snapshot.box/#/s:aave.eth/proposal/0x9d9972d206108c73dc35fd6b7f598a76705aefadd66caea748c41194434fa77d). Vote will start tomorrow, we encourage everyone to participate. ---
**Author:** ![ACI](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/aci/32/4780_2.png) [@ACI](https://governance.aave.com/u/ACI)\ **Post date:** [March 15, 2025, 7:58am UTC](https://governance.aave.com/t/arfc-recognize-hyperlend-as-a-friendly-fork/21129/3 "2025-03-15T07:58:06Z")
After Snapshot monitoring, the current [ARFC Snapshot](https://snapshot.box/#/s:aave.eth/proposal/0x9d9972d206108c73dc35fd6b7f598a76705aefadd66caea748c41194434fa77d) ended recently, reaching out both Quorum and YAE as winning option, with 853.5K votes. Therefore [[ARFC] Recognize HyperLend as a Friendly Fork ](https://governance.aave.com/t/arfc-recognize-hyperlend-as-a-friendly-fork/21129) has PASSED. Next step will be the publication of an AIP for final enforcement and confirmation of the proposal. ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/aave/original/2X/e/e11637c36f45ffa158f2146f5c19438d46e0824d.svg) [@system](https://governance.aave.com/u/system)\ **Post date:** [April 14, 2025, 7:58am UTC](https://governance.aave.com/t/arfc-recognize-hyperlend-as-a-friendly-fork/21129/4 "2025-04-14T07:58:15Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. ---
**Author:** ![ACI](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/aci/32/4780_2.png) [@ACI](https://governance.aave.com/u/ACI)\ **Post date:** [March 10, 2026, 12:01pm UTC](https://governance.aave.com/t/arfc-recognize-hyperlend-as-a-friendly-fork/21129/5 "2026-03-10T12:01:34Z")
ACI believes that, in order to ensure that **compliant friendly forks** are not exposed to vulnerabilities patched during upgrades,it was needed to update the current proposal to allow compliant forks such as Hyperlend to use the most recent Aave version at the discretion of the DAO service providers. As Hyperlend has been fully compliant with the friendly fork framework we have informed them that they can upgrade to current versions of aave codebase at their discretion.