# \[TEMP CHECK\] Recognize HyperLend as a Friendly Fork

**URL:** <https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969>\
**Category:** Governance\
**Created:** [February 7, 2025, 1:07pm UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969 "2025-02-07T13:07:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![hyperlend](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/hyperlend/32/8950_2.png) [@hyperlend](https://governance.aave.com/u/hyperlend)\
**Post date:** [February 7, 2025, 1:07pm UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/1 "2025-02-07T13:07:37Z")

</div>

Author: HyperLend Team ([0xNessus](https://x.com/0xNessus) and [fbsloXBT](https://x.com/fbsloXBT))  
Date: 2025-02-06T23:00:00Z

* * *

### Summary

This proposal seeks to recognize [HyperLend](https://www.hyperlend.finance/) as a friendly fork of Aave, deployed on the Hyperliquid EVM chain (HyperEVM).

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.

### Motivation

##### About HyperLend:

This proposal seeks to establish HyperLend as a friendly fork of Aave, deploying multi-asset pools on HyperEVM to become the leading money market on the network.

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
- notify HyperLend of any potential security issues found in the Aave codebase, so we can mitigate them before they are publicly disclosed

### Next Steps

- Receive the feedback from the Aave community
- Escalate this proposal to a Temp Check Snapshot
- If Temp Check snapshot passes:
  - publish an ARFC forum post
  - escalate the proposal to an ARFC snapshot

### Copyright

Copyright and related rights waived via CC0.

---

<div class="post-metadata">

**Author:** ![EzR3aL](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/ezr3al/32/10721_2.png) [@EzR3aL](https://governance.aave.com/u/EzR3aL)\
**Post date:** [February 9, 2025, 5:26pm UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/2 "2025-02-09T17:26:40Z")

</div>

Hello and thank you for the proposal.  
I appreciate that another fork is coming to the DAO to propose fee sharing as outlined in the [Aave fork framework](https://governance.aave.com/t/arfc-framework-for-instances-and-friendly-forks/19659).

The specification seem to match our framework which is needed to be accepted.  
The only thing im not sure about is this part:

> [@hyperlend](#):
>
> notify HyperLend of any potential security issues found in the Aave codebase, so we can mitigate them before they are publicly disclosed

But I do think other SP might be able to clarify how this is currently being done with other forks.

---

<div class="post-metadata">

**Author:** ![MarcZeller](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/marczeller/32/7124_2.png) [@MarcZeller](https://governance.aave.com/u/MarcZeller)\
**Post date:** [February 11, 2025, 9:29am UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/3 "2025-02-11T09:29:46Z")

</div>

In case of Friendly fork, the forks will be informed of any issue or known vulnerability as best as risk service providers can provide the information in reasonable timeframes.

the DAO used to do it for everyone, but ACI got tired of saving Radiant ass for zero benefit (even net negative). they got hacked shortly after we removed the training wheels.

---

<div class="post-metadata">

**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 13, 2025, 2:36pm UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/4 "2025-02-13T14:36:32Z")

</div>

The current proposal has been escalated to [TEMP CHECK Snapshot](https://snapshot.box/#/s:aave.eth/proposal/0xca4b2ab3f17c3e670b8c661392cc15c739b66c0458ff784cfe474aaa686792b6), as part of Skywards.

Vote will start tomorrow, we encourage everyone to participate.

---

<div class="post-metadata">

**Author:** ![Michigan\_Blockchain](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/michigan_blockchain/32/7913_2.png) [@Michigan\_Blockchain](https://governance.aave.com/u/Michigan_Blockchain)\
**Post date:** [February 17, 2025, 4:36am UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/5 "2025-02-17T04:36:23Z")

</div>

As Michigan Blockchain, we support recognizing HyperLend as a friendly fork of Aave on Hyperliquid EVM (HyperEVM). We believe that this collaboration will benefit both Aave and HyperLend, and further create a mutually beneficial partnership. This partnership will extend Aave’s influence into the growing HyperEVM ecosystem. HyperLend has already demonstrated strong adoption on testnet, with over 200k users, and is backed by top-tier partners and risk managers. By sharing 10% of protocol revenue, allocating 3.5% of its token supply to Aave DAO, and airdropping 1% of HPL tokens to stkAAVE holders, HyperLend will align itself closely with Aave’s community and stakeholders.

**![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXflvHR9_W04qJ3am5mm81WQPiWfmP9CaYUtHSE7ln-qr1ANLTupRrAfyGjG46JFY4Yqr-yLvDTtW8ZzTh_fxowPqn7vyEmxXTMQLs3PVBhhMLfejutMsXRdBjr2efUHpHzckTqgbA?key=zFUKX89QeH_tE8de1cCyvZi6)**  
HyperLend TVL (USD) for the last 3 months (Dec 16 to Feb 16). Source: HyperLend Analytics

Aave will also capture additional value and in parallel strengthen its reputation as the foundational lending protocol in DeFi. Granting code access and early security notifications to HyperLend will furthermore foster trust and innovation without unnecessary risks. We believe this partnership is a win-win for both ecosystems.

-Kerem Dillice and nsks

---

<div class="post-metadata">

**Author:** ![sid\_areta](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/sid_areta/32/5220_2.png) [@sid\_areta](https://governance.aave.com/u/sid_areta)\
**Post date:** [February 17, 2025, 10:31am UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/6 "2025-02-17T10:31:21Z")

</div>

We’re in favour of ensuring a friendly relationship with Aave’s forks - the profit sharing is in alignment with the Fork Framework.

---

<div class="post-metadata">

**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, 7:54am UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/7 "2025-02-18T07:54:32Z")

</div>

After Snapshot monitoring, the current [TEMP CHECK Snapshot](https://snapshot.box/#/s:aave.eth/proposal/0xca4b2ab3f17c3e670b8c661392cc15c739b66c0458ff784cfe474aaa686792b6) ended recently, reaching out both Quorum and YAE as winning option, with 747.8K votes.

Therefore, [[TEMP CHECK] Recognize HyperLend as a Friendly Fork ](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969) has PASSED.

Next step will be the publication of an ARFC to continue gathering interest from both community and Service Providers and refine proposal, before moving forward through governance.

Closing thread to continue discussion on ARFC.

---

<div class="post-metadata">

**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, 7:54am UTC](https://governance.aave.com/t/temp-check-recognize-hyperlend-as-a-friendly-fork/20969/8 "2025-02-18T07:54:45Z")

</div>


