[ARFC] Add PEPE to Aave V3

[ARFC] Add PEPE to Aave V3

Author: ACI ( Aave Chan Initiative)

Date: 20235-05-12


Summary

This is a proposal to add PEPE as a supported collateral asset on Aave, after successful [TEMP CHECK] Add PEPE as a Supported Asset on AAVE and its correlative TEMP CHECK Snapshot.

Motivation

PEPE is a widely held, highly liquid asset in the crypto ecosystem. Its rapid growth in adoption, substantial trading volumes, and deep liquidity across major centralized and decentralized exchanges make it a natural candidate for integration into AAVE.

Adding PEPE could:

  • Expand AAVE’s market reach and attract a new demographic of depositors and borrowers.
  • Help fuel the growth of GHO, AAVE’s native stablecoin, by increasing the available collateral base for GHO minting.
  • Generate additional liquidation income for the AAVE protocol. Given PEPE’s nature as a meme-driven asset, it is reasonable to expect elevated levels of borrowing, speculation, and resulting liquidations — all of which could accrue value to the AAVE DAO.
  • Further diversify the asset options available to users while carefully managing risk through isolated market controls.

Specification

Risk Parameters will be provided by Risk Service Providers and ARFC will be updated accordingly.

Disclaimer

The proposal is directly powered by ACI, under Skyward. ACI did not received compensation for the creation of this proposal.

Next Steps

  1. 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.

1 Like

Which market is this listing for?

2 Likes

Memes should have a separate market.

As the original poster of the TEMP CHECK, I want to first thank everyone for the thoughtful feedback and discussion on the PEPE proposal. I appreciate the diverse perspectives shared and would like to address some of the concerns raised:

1. Reputational Considerations:

I understand the apprehension regarding the inclusion of meme coins like PEPE in AAVE’s core markets. However, it’s worth noting that traditional financial platforms, such as Charles Schwab, offer a wide range of assets—from blue-chip stocks like MSFT and AAPL to more speculative penny stocks. This diversity doesn’t necessarily tarnish their reputation; instead, it caters to a broader user base.

Similarly, casinos provide both high-stakes games and penny slots, with the latter often being significant profit centers. The key is in offering choices while managing risks appropriately.

2. Risk Management:

Conservative risk parameters, such as Loan-to-Value ratios and liquidation thresholds, would be recommended by risk management partners to mitigate potential volatility. As long as we set the parameters correctly — we can dramatically reduce the risk of bad debt.

3. Revenue Opportunities:

Incorporating PEPE could open up new revenue streams for AAVE:

  • GHO Growth: By allowing users to deposit PEPE and borrow GHO, we can increase the utility and adoption of AAVE’s native stablecoin.

  • Liquidation Income: Given the speculative nature of meme coins, there’s a higher likelihood of liquidations, which can generate additional income for the protocol.

4. Market Demand:

PEPE has demonstrated substantial trading volumes and liquidity across major exchanges. Its inclusion could attract a new demographic of users to AAVE, expanding our community and user base.

In Conclusion:

The integration of PEPE, when approached with caution and strategic risk management, presents an opportunity to diversify AAVE’s offerings and tap into new markets. I welcome further discussions on this and am open to collaborating on refining the proposal to address any outstanding concerns.

3 Likes

Hello, I’m rather in favor of this proposal, with the necessary risk management, of course.

However, even if the addition of PEPE were to take place on the main instance, I believe it’s important to clarify from the start that this would ONLY be in a testing context, and that if the results are conclusive and the DAO wishes to further develop the memecoin market on the platform, a dedicated instance for memecoins should be created in order to separate these assets from the rest of the protocol.

In my opinion, the memecoin market is significant and worth considering due to the volumes generated and the potential revenue it could bring to the DAO. With support from platforms like Contango, traders could easily trade these assets directly through AAVE, whereas other major money markets do not currently offer them.

It might also be interesting to look at the case of Kamino on Solana, which lists memecoins on its lending platform and, to my knowledge, hasn’t encountered any major issues so far.

1 Like

Hello everyone,

Since Aave 3.2 introduced Liquid emodes, we have gained the benefits of instance segregation by locking up collateral with debt assets in pairs without the downside of splitting liquidity across separate instances. Consequently, onboarding can occur on any instance without penalty.

My two cents:

  1. Demand is on mainnet.
  2. Prime is viewed as a highly curated market with a smaller asset selection. Onboarding PEPE there might send the wrong message.
  3. Core is more open but only native GHO minting is available. This setup with V3 does not allow adding a risk premium to the GHO borrow rate.
  4. I suggest onboarding ahead of this AIP a wrapped GHO, wGHO, in Core with a bespoke interest rate strategy. I would like @ChaosLabs to implement an Edge Oracle on this debt asset that mirrors the GHO borrow rate plus a premium.
  5. The DAO currently provides liquidity in Prime. The DAO should also LP in wGHO. I recommend creating a junior risk tranche for StkGHO by covering wGHO separately from GHO under an umbrella.
  6. If the PEPE experiment succeeds, expand long tail collateral wGHO onboardings to boost protocol revenue while keeping risk in check.
  7. For wStkGHO stakers, since the wGHO borrow rate exceeds the GHO minting cost, they should earn more than StkGHO stakers, compensating them for the added risk via higher yield.
  8. For those familiar with the ACI vision, this essentially revives the emergence instance concept, monetizing long tail assets in a structure that offers higher profit margins for those assets.

@bgdlabs @ChaosLabs @TokenLogic @LlamaRisk

4 Likes

Hello @Leritu and @MarcZeller .
How much demand do you think it is?

Summary

LlamaRisk concludes that PEPE can be onboarded with conservative parameterization but underscores crucial optics and strategic implications.

Onboarding a memecoin like PEPE establishes a significant precedent, likely encouraging further memecoin onboarding requests. This will inevitably shape Aave’s DeFi industry perception and introduce reputational risk. Aave’s architecture was not initially envisioned for such assets. Even with carefully managed risk parameters, this nuance may be lost on casual observers, potentially diminishing Aave’s perceived creditworthiness. The DAO must factor this reputational cost into its decision-making process. Therefore, to mitigate the reputational impact, we believe that PEPE should not be onboarded to the Aave Core instance or be approved as collateral for GHO minting.

We endorse the “emergence instance” concept proposed by ACI, having independently developed an onboarding/off-boarding framework for this use case. PEPE necessitates a distinct risk premium, which must be actualized through its interest rate model; a separate instance is the most suitable environment to implement this specific requirement. We propose PEPE as the inaugural asset for such an instance. This approach circumvents complexities tied to wGHO and risk tranching proposed for stkGHO. We reiterate our position against using PEPE for GHO minting.

Beyond these strategic points, PEPE’s technical onboarding is manageable. The principal conventional risk is its pronounced volatility, with the asset’s price capable of significant short-term fluctuations. This presents a potential risk to profitable liquidations, necessitating conservative supply and borrow caps, a low debt ceiling, cautious Loan-to-Value ratios (LTVs), and an interest rate model designed for appropriate revenue generation relative to risk.

Fundamentally, PEPE is a relatively uncomplicated asset. It possesses strong liquidity, both on-chain and off-chain and its developers have renounced all ownership. It introduces no new dependencies, and its architecture is simple. This inherent simplicity curtails risk. Given these immutable characteristics, the primary risk exposure for Aave, should it be onboarded, is market volatility.

Collateral Risk Assessment

1. Asset Fundamental Characteristics

1.1 Asset

PEPE is a memecoin deployed on Ethereum on April 14, 2023. It is ERC20 compliant and has a total supply of 420,690,000,000,000. It is loosely associated with Pepe the Frog, a cartoon character first drawn in 2005.

As a “memecoin”, this is a novel asset class to bring to Aave. This asset is conceptually straightforward and has no attached revenue source or staking ability. Multiple derivative PEPE tokens exist, but they have yet to see the same level of product-market fit as PEPE itself.

There are a variety of major use cases for onboarding this asset.

A user already holding this asset may wish to increase their exposure and borrow stablecoins against it, which may be swapped for more PEPE and redeposited to Aave. This is a form of leverage trading, a use case for which lending protocols offer a compelling alternative to perpetual exchanges for traders looking to pay less in funding in exchange for more conservative LTVs. Users may also use stablecoins for any other purpose, such as to access value without incurring a taxable event or sale of PEPE.

Alternatively, users may look to short PEPE by borrowing the asset, selling it for an asset they believe will appreciate relative to PEPE then resupplying it to Aave. Users already holding PEPE looking to hedge against price depreciation may short the asset and reduce price delta exposure.

1.2 Architecture

PEPE’s architecture is straightforward. It is a token that self-describes in the following way:

$PEPE is a meme coin with no intrinsic value or expectation of financial return. There is no formal team or roadmap. The coin is completely useless and for entertainment purposes only.


Source: Pepe Roadmap, Pepe.VIP

To achieve this aim, their team has outlined a roadmap. Its clarity and simplicity are notable in an ever-increasing complexity and integration environment.

This architecture presents a limited risk to Aave.

1.3 Tokenomics


Source: Tokenomics, Pepe.VIP

PEPE’s tokenomics are similarly straightforward, with a 420,690,000,000,000 total supply. The team reported that an amount was locked into initial liquidity pools on launch. The incredibly high number of tokens results in a result confusing for non-sophisticated actors, adding risk. It is likely set that high to take advantage of unit bias, where speculators see a low unit price and decide it is a good investment (irrespective of market capitalization).

For reference, the “No Taxes” comment refers to trading taxes that some memecoins use to burn an amount of the memecoin in the trade. This is designed to increase the token’s price by reducing the overall supply.

1.3.1 Token Holder Concentration


Source: Pepe Token Holder Distribution, Etherscan,, May 14th, 2025

Pepe is well distributed amongst CEXes and other venues. Its distribution is comparable to other leading ETH-centric memecoins.

2. Market Risk

2.1 Liquidity


Source: Pepe Liquidity, DeFiLlama Liquidity, May 12, 2025

Pepe is sufficiently liquid on Mainnet, with a $11M trade resulting in ±7.5% price impact.

2.1.1 Liquidity Venue Concentration


Source: Pepe Liquidity, Odos, May 12, 2025

The vast majority of PEPE liquidity is concentrated into a Uniswap V2 pool(~$52M), which is supported by a Uniswap V3 pool, a Hashflow pool and a selection of others.

2.1.2 DEX LP Concentration


Source: Top 100 Uniswap V2 Pepe-WETH LP token holders, Etherscan, May 12th, 2025

The PEPE contract address holds nearly 100% of onchain liquidity in this pool. This amount was added at launch and has not been touched since. While nearly all this liquidity being held in one address presents risk, the fact that it is “locked” (see section 4) means that this liquidity cannot be pulled. Given that it is a Uniswap V2 position, this liquidity is full range and indiscriminate (as opposed to the more discriminate V3 positions that may pull liquidity should the price move out of range).

2.2 Volatility


Source: PEPE/USD, GeckoTerminal, May 14th 2025

PEPE is highly volatile, with its token price doubling (and halving) in under 10 days in May 2024. This level of volatility could present a risk to profitable liquidation should liquidity not be locked in the token contract itself.

2.3 Exchanges


Source: Pepe Exchanges, Coingecko, 12 May 2025

Pepe is traded on many centralized exchanges and is very liquid. Volumes on this token are extremely high (>$1B / daily). This indicates a strong demand to speculate on this token. 2% price impact is cumulative ~$30M, indicating good liquidity.

2.4 Growth


Source: Pepe Market Capitalization, Coingecko, 12 May 2025

Pepe’s market capitalization has grown in lockstep with its token price. It has grown modestly over the past year ($4B to $5.8B), with significant upwards growth in between (up to $11B).


Source: Addresses by Time Held, IntoTheBlock, May 13th, 2025

3. Technological Risk

3.1 Smart Contract Risk

One audit by CertiK for this token is documented, though this audit was post-deployment. It found one issue, which was resolved by renouncing ownership of the contract.

3.2 Bug Bounty Program

No bug bounty program is documented.

3.3 Price Feed Risk

Pepe does not have a mainnet Chainlink price feed. Feeds on Arbitrum, Optimism, and zkSync are available. This would need to be streamed to the mainnet for Aave to facilitate the asset’s onboarding. This is a market price feed.

3.4 Dependency Risk

As a memecoin, this token introduces no dependencies that Aave has not already exposed to.

4. Counterparty Risk

4.1 Governance and Regulatory Risk

Pepe has no governance or ownership. All contract control was renounced in April 2023. No aspect of the contract may be modified.

The recent Staff Statement issued by the U.S. Securities and Exchange Commission concerning so‑called “meme coins” bears directly on the legal characterization of these tokens, even though any effort to tether their issuers to a single domestic legal regime is likely to prove impracticable.

In that statement, the Division of Corporation Finance signals that, in most fact patterns, meme‑coin tokens such as PEPE—do not meet the definitional threshold of a “security.” Where a token is marketed chiefly for entertainment or speculative purposes, carries no expectation of profit derived from managerial or entrepreneurial efforts, confers no right to income, dividends, or business assets, and offers little functional utility beyond its exchange value and cultural cachet, the Division would generally not expect the offer or sale of the token to require registration under the Securities Act. The SEC likewise reserves the right to revisit that position should the “economic reality” shift—for example, if proceeds are pooled for a commercial venture or if token holders begin to share in profits generated by a promoter’s efforts—thereby bringing the asset within the ambit of the Howey test.

By contrast, the Commodity Futures Trading Commission adopts a broader lens: virtual currencies are presumptively treated as “commodities” under Section 1a(9) of the Commodity Exchange Act. Judicial precedent and CFTC enforcement activity—spanning Bitcoin, Ether, Litecoin, Tether, and other digital assets—confirm that meme‑coin tokens such as PEPE likewise fall within the statute’s commodity definition so long as they function primarily as a medium of exchange or store of value. In its submission to list an event contract referencing PEPE, Crypto.com cited previous CFTC proceedings, including CFTC v. Binance, to underscore that no federal regulator has reclassified PEPE as anything other than a commodity. Consequently, derivative instruments referencing PEPE—futures, swaps, or event contracts—remain subject to the CFTC’s supervisory jurisdiction.

4.2 Access Control Risk

4.2.1 Contract Modification Options

This contract may not be modified in any way, given that ownership was renounced. Should it not have been, key functions include a token blacklist function, a burn function, a transfer ownership function and a renounce ownership function, which was called at 0x91c9a6caf8e7b5419a7e597982a0cf9b4fc01413279ab840bb57a2e9c528f252.

4.2.2 Timelock Duration and Function

N/A

4.2.3 Multisig Threshold / Signer identity

N/A

Note: This assessment follows the LLR-Aave Framework, a comprehensive methodology for asset onboarding and parameterization in Aave V3. This framework is continuously updated and available here.

Aave V3 Specific Parameters

To be provided in collaboration with @ChaosLabs.

Price feed Recommendation

LlamaRisk recommends that the PEPE/USD Chainlink feed be posted to Ethereum and used to support this Ethereum market.

Disclaimer

This review was independently prepared by LlamaRisk, a community-led decentralized organization funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.

The information provided should not be construed as legal, financial, tax, or professional advice.

5 Likes

After reading some more comments about this listing and the risk assessment from LlamaRisk my vote will be NO.
While I do think there might be a market to explore we shouldn’t have so called long tail assets like Pepe in Aaves main market. Even though liquid eModes do offer us options to mitigate risk and connect these assets for example with GHO im unsure what this will do to the reputation of Aave. Aave v4 or a dedicated market would be better for these kind of assets. Aave has been always the app of trust and security because it wasn’t listing any asset.
A dedicated market, just for visibility and testing purposes and I might be open for a test.

4 Likes

The concept of using wGHO to create a new premium risk tier has been discussed extensively over the last 6 months. There is a lot of merit to this concept.

An alternative concept that uses stataGHO from Prime as a deposit asset on Core with v3.2 eModes is also valid. The facilitator on Prime can control supply of GHO to optimise the borrow rate and reduce overall volatility, whilst the interest rate on Core for stataGHO enables a risk premium to be achieved. The flow of funds is to deposit GHO into Prime, receive stataGHO and deposit this stataGHO on Core enabling users earning Prime Deposit Rate plus the stataGHO deposit rate on Core. The frontend would abstract this away with users simply depositing GHO into stataGHO reserve on Core.

Both options utilise v3.2 eModes to control the risk exposure which offers a lot more granularity than a general listing or Isolation Mode. wGHO is likely to be the cleaner and more easy to implement solution of the two concepts. Furthermore, wGHO can also be added to Isolation Mode which enables other long tail assets to access the liquidity within existing parameter constraints.

Introducing new types of collateral supportive of minting GHO is interesting from a demand perspective and whilst demand for GHO debt is strong, there is more upside by creating additional utility for GHO. The creation of wGHO creates new utility and is expected to offer more yield than Prime, more yield than sGHO and probably less yield than stkGHO via Umbrella. The premise of new higher risk tier than stkGHO, wstkGHO creates another use case for GHO.

Given wstkGHO is funded from Revenue, it presents an interesting choice for DAO funds to supplement/bootstrap the coverage. Note, stkGHO is 12M via Umbrella and wstkGHO would likely be even less. The DAO could likely fund the majority of wstkGHO liquidity needs.

Similar to @LlamaRisk, I share the opinion we should pursue other means of bootstrapping liquidity in the wGHO reserve. This is partially optics for how it could affect GHO and also, there is ample demand from existing assets which diminishes the upside.

One of the main benefits from creating wGHO is the higher deposit yield for GHO holders. Generally, we need more GHO use cases relative to issuing new supply. An initial step would be to consider wGHO as a debt asset for collateral types in isolation mode. ie: Migrate USDC and USDT debt collateralised by isolated assets to wGHO debt. I expect this to be a net positive for the peg.

There is strong demand for stablecoins from higher risk profile assets and various CEX accept these types of collateral, often at lower funding rates and lesser LT than what is being discussed above. It is unclear how much of the Defi and CEX user base overlaps for long tail assets. However, the inclusion of meme coins is likely to increases the perceived risk profile of the Core instance.

Personally, at this point in time, the upside from listing PEPE is questionable and initial steps favour re-thinking existing assets listed in Isolation mode and how we can migrate the associated debt to using wGHO debt.

At @TokenLogic we support the general direction outlined by @MarcZeller for Aave and prefer to explore other options before onboarding PEPE. If new information emerges, such as committed demand for wGHO upon listing, then we are willing to revisit this and in the interim we maintain our NAY vote preference.

5 Likes

look like we lack consensus on this one.

Let’s kill the proposal but salvage the good part of the discussion to build the Emergence instance,

instead of PEPE, we can onboard there all the current isolation mode tokens we have on Core to lock them with GHO. This will clean up Core and increase our margins on these collateral, currently with a terrible Risk/Revenue ratio (UNI as an example is generating less than 10k$/year of revenue currently)

@MatthewGraham’s remark on stataGHO is good, but in terms of UX/UI, we need to abstract native yield to make the cost of borrowing more readable for the user. Likewise, the app should “unwrap” borrowed StataGHO and deliver to the borrower plain GHO.

debt is shown in GHO even if at protocol level it’s stataGHO, interest rate is simply plain borrow cost + stataGHO yield. (Real math is a bit more complex than this but this is the big picture)

It’s not rocket science, but I doubt @AaveLabs can deliver this in a reasonable amount of time. Maybe it’s something to build with a third-party app?

1 Like