Temp Check / Discussion: Exploration of Aave Deployment on Cardano (Feasibility Study Proposal)

Other
1

Summary

This ARC proposes initiating a structured feasibility study to evaluate the potential deployment of Aave on Cardano.

The objective is to assess:

  • Technical compatibility

  • Risk framework requirements

  • Liquidity and market viability

This is the first step to determine whether further exploration is justified.

Motivation

Aave has successfully expanded across multiple EVM-compatible networks. However, the broader DeFi ecosystem remains concentrated around a single execution paradigm.

At the same time, alternative blockchain architectures have matured. Cardano represents one such environment, characterized by:

  • eUTXO-based transaction model

  • Functional programming approach to smart contracts

  • Emphasis on deterministic execution and formal methods

  • High levels of validator decentralization

Despite these properties, DeFi activity and TVL on Cardano remain relatively limited compared to other ecosystems.

This creates a potential opportunity to evaluate whether:

  • Aave could act as a foundational DeFi primitive in that environment

  • A new user and liquidity segment could be accessed

  • Architectural diversification could provide strategic value

Strategic Considerations

1. Architectural Diversification

Exploring deployment outside the EVM ecosystem may:

  • Reduce reliance on a single execution model

  • Provide exposure to alternative design trade-offs

2. Early Positioning in an Underdeveloped DeFi Market

Cardano currently lacks mature lending infrastructure at scale.
Aave could potentially:

  • Establish early presence

  • Define risk and collateral standards in a new environment

3. Emerging Collateral Opportunities (Forward-Looking)

There is ongoing development in the Cardano ecosystem around non-custodial Bitcoin interoperability, including approaches leveraging Zero-Knowledge technologies.

If successful, this could enable:

  • Use of BTC as collateral without custodial bridges

  • Reduced counterparty risk compared to wrapped assets

While early-stage, this direction may represent a differentiated collateral landscape worth monitoring.

Specification (Feasibility Study Scope)

This ARC proposes conducting a 6–8 week feasibility study covering:

Technical Assessment

  • Mapping Aave architecture to Cardano’s eUTXO model

  • Evaluation of smart contract design constraints

  • Identification of required adaptations or redesigns

Risk & Oracle Framework

  • Oracle availability and reliability

  • Liquidation mechanisms under eUTXO constraints

  • Risk parameter modeling

Market & Liquidity Analysis

  • Current DeFi activity and liquidity depth

  • Potential collateral assets

  • Incentive requirements for market bootstrapping

Ecosystem Dependencies

  • Required infrastructure (indexing, analytics, tooling)

  • Potential collaborators within the Cardano ecosystem

Implementation Considerations

Execution of the feasibility study could be carried out by:

  • Independent contributors

  • Ecosystem-aligned teams

  • External service providers

Subject to community alignment, a follow-up proposal (ARFC) would define:

  • Selected contributors

  • Detailed scope

  • Budget and timeline

Risks

Technical Complexity

  • Fundamental differences between account-based and eUTXO models

  • Potential need for partial or full redesign of components

Liquidity Fragmentation

  • Limited existing DeFi liquidity on Cardano

  • Dependence on incentives and ecosystem coordination

Opportunity Cost

  • Resource allocation vs. expanding within existing EVM ecosystems

Ecosystem Maturity

  • Tooling, oracle infrastructure, and integrations may require additional development

Cost & Funding

This ARC does not request funding.

If the community supports proceeding, a future ARFC would include:

  • A project submission on Project Catalyst to fund the initiative

Next Steps

This ARC seeks feedback from the community on:

  • Whether exploring a non-EVM deployment aligns with Aave’s strategy

  • Whether Cardano is a relevant ecosystem to evaluate

  • Whether the proposed feasibility study scope is appropriate

If there is sufficient support, the next step would be:
→ Drafting an ARFC with defined contributors, scope, and funding requirements.

Conclusion

This proposal does not advocate immediate deployment, but rather a structured evaluation of a potential strategic expansion.

The goal is to determine whether Cardano represents:

  • A viable new market for Aave

  • A meaningful diversification of execution environments

  • A forward-looking opportunity tied to emerging collateral models

Community feedback will determine whether further steps are warranted.

1 Like
2

The Kelp DAO exploit of April 2026 demonstrated that Aave’s risk is not isolated it is directly tied to the security assumptions of every integrated protocol. Deploying on Cardano would introduce bridge dependencies and oracle frameworks that are far less battle-tested than existing EVM integrations. Before a feasibility study, the community should honestly assess what is Aave’s risk tolerance for another contagion event from a nascent ecosystem..? @Diegotowers

3

Hi, if you want to make a proposal then please follow the guidelines. Please change this post. It’s pinned at the front/homepage.

Thank you.

4

Thanks for raising this — fully agree on your point about Aave’s risk surface.

That said, a deployment on Cardano wouldn’t necessarily require the same dependency stack as EVM environments. An approach could focus on native assets and a minimal set of integrations, avoiding bridges altogether.

Not risk-free, of course, but potentially a more contained setup to evaluate. I think this is exactly the kind of trade-off a feasibility study should help clarify.

Appreciate you taking the time to reply :slightly_smiling_face:

1 Like
5

Hi, thanks for the guidance.

I’ve updated the title to Temp Check / Discussion to better reflect the intent.
From my side, I’m not fully seeing what else might be out of line with the guidelines.

Would you mind pointing me to any specific sections or changes I should make?

Happy to adjust accordingly — just want to make sure I’m aligned with the expected format.

Thanks :folded_hands:

1 Like
6

The April 18 Kelp incident did not break Aave’s contracts; it was a cross-chain messaging.
Even though Aave’s loan book sits across 22 chains. It is not real diversification. It is a nominal multi-chain presence on top of a deeply concentrated, EVM-bridge-dependent risk surface.

A Cardano deployment built on native assets only, which is exactly what @Diegotowers clarified in his reply, does not add to that surface. It sits outside of it. That is a contained risk perimeter, not a theoretical one.

On the technical side:
The eUTXO model removes exploit primitives that have repeatedly hit Aave forks. Plutus scripts validate whether a UTXO can be spent, but they cannot initiate calls into other contracts during execution. Reentrancy as a class is gone. The original DAO hack, bZx, and Cream Finance all rely on a primitive that does not exist on Cardano.

Validation is also deterministic. A transaction’s outcome can be verified off-chain before it is broadcast. If inputs are stale or constraints fail, validation fails locally at zero cost. Forged-message attacks like Kelp’s work precisely because the verifier accepts a state it cannot independently re-derive. eUTXO forces validators to reference specific consumed UTXOs, which makes that whole class of attack much harder to pull off in the first place.

Formal verification is genuinely tractable here too, not as a marketing line. Plutus scripts are pure functions over (datum, redeemer, context), which is the exact model under which mathematical correctness proofs are feasible. That is also why Franklin Templeton already runs a Cardano node.

These are not claims on paper. Cardano DeFi has been live for around three years and has not had a single major reentrancy or oracle-manipulation exploit at scale.

On market timing:
Diego’s argument about triggering widespread adoption has a precedent: Aave on Arbitrum.
Cardano DeFi numbers as of April 2026 are at roughly the same stage Arbitrum was in early 2022.

On opportunity cost:
The December 2025 multichain temp-check showed several Aave deployments (Polygon, Gnosis, BNB, OP, Scroll, Sonic, Celo) generating less than $3M in annualized revenue, with the proposal explicitly recommending Reserve Factor increases in those instances. Soneium sits at $4M in TVL and $51K in annualized revenue. Metis is at $8M TVL and $3.3K. That is the realistic ceiling of what additional EVM L2 listings now look like. A no-funding feasibility study on a non-EVM chain with $130M+ in existing DeFi TVL, an underdeveloped lending market, and a near-term BTC collateral pipeline is a meaningfully better use of governance bandwidth than another L2 listing.

In favor of moving to ARFC.

Cheers!

2 Likes
7

Thank you for this detailed and well-reasoned response. Your point on eUTXO eliminating reentrancy as an exploit class, and the deterministic validation argument against forged-message attacks, strengthens the technical case significantly.

The opportunity cost framing comparing Cardano DeFi’s current stage to Arbitrum in early 2022, alongside the low revenue ceilings of existing EVM L2 deployments is exactly the kind of governance-relevant context this discussion needed.

Support for moving to ARFC. Looking forward to building on this momentum. @qfedesq