Aave Integration for Fintechs, Wallets and Funds
Protofire builds what Aave leaves to fintechs, wallets and funds on its markets. That is client position booking, transactions signed by their own wallet, and alerts on health factors and parameter changes. We built the LandX Credit Gateway on Arenas, our lending stack on forked Aave V3 contracts.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What Aave's contracts keep and what your firm books
In an Aave integration, Aave's contracts keep each client position, and your firm has to book it. Aave Labs says in its terms that it "does not own, operate or control the Aave Protocol". Aave Labs also says that it does not "determine, prevent or reverse liquidations".
Aave's API and MCP server return unsigned transactions. So your own Safe, MPC wallet or custody vault signs each write.
For example, your product supplies and borrows on Aave. Then a client's collateral is liquidated by a transaction that your wallet did not sign, and your ledger holds no entry for that liquidation.
Who owns each part, from Aave to your ledger
Protofire's transaction builder hands unsigned plans to your signer, and your wallet sends them to Aave. Positions, parameter changes and liquidations are read back from Aave.
Client ledger
Signer
Aave V3 markets and V4 hubs and spokes
DAO votes, stewards and emergency multisigs
Horizon allowlist and issuer roles
Position reader and ledger feed
Transaction builder
Watcher for parameter changes
Aave position changes that your ledger does not see
Your ledger does not see three kinds of change to a client's Aave position.First, the balances of aTokens and variable debt tokens grow as blocks pass, and Aave does not post that growth to your books. Second, a steward can cut a cap or an LTV inside set bounds with no vote, and a freeze applies the moment it is sent. Third, a liquidation comes from an outside liquidator.
If no one books balance growth, steward changes and liquidations, a client's statement shows whatever someone last copied from Aave's app. Your client limits do not follow a cap that was cut on Tuesday. An app that greys out a frozen reserve blocks a repayment that still works on Aave. A frozen reserve stops new supply and borrows but still lets a position repay and withdraw (Aave).
On Horizon, the market for tokenized funds, the fund's issuer also holds a role over the borrower's position.
Aave governance, versions, networks and developer access
- Governance
- In the Aave DAO, AAVE, stkAAVE and aAAVE holders on Ethereum propose, discuss, vote on and execute protocol changes (governance).
- Versions
- Aave V3 runs in more than one revision. V3.7 was rolled out by 29 May 2026, and some instances still run V3.6. Aave V4 has been live on Ethereum since 30 March 2026 (changelog).
- Networks
- V4 runs on Ethereum, Avalanche, Arc and Base. Base was added on 7 October 2026 (changelog).
- Developer access
- The tools are AaveKit for React and TypeScript, a GraphQL API for V3 and V4 with "No API key required", and Solidity interfaces. An MCP server prepares unsigned transactions (docs index).
- Horizon
- Horizon is "An Aave Labs initiative". It is a separate instance of the Aave Protocol on Ethereum, where USDC, RLUSD and GHO can be borrowed. A NAV outside its bounds is rejected, and the last valid price is kept (Horizon).
Checked November 2026 against Aave's documentation.
What you get from an Aave integration with Protofire
Each client's share of an Aave position, booked in your ledger
Your finance team no longer reads balances off Aave's app. Protofire builds the position reader and ledger feed. The reader takes supply, debt, collateral and health factor per address, market and spoke from Aave's API and checks them against the chain. The feed posts each activity once under its Aave activity id. The feed books interest to your cut-off instead of to UTC.
Each transaction signed by your own wallet
Your approval rules apply to each supply, borrow, repay and withdraw. Protofire builds the transaction builder, which hands unsigned plans to your Safe, MPC wallet or custody platform. Each plan includes the ERC-20 approval that Aave's execution plan asks for first. A broadcast that times out is looked up by the signer's nonce and the transaction hash before a resend.
Alerts at the health-factor levels your risk team sets
Protofire's watcher sends alerts at the health-factor levels that your risk team sets. Health factors in the watcher use the price that Aave's oracle gives each reserve, which is the price that liquidations run on. Those health factors are kept apart from the price at which your finance team values positions. Each alert names the clients it affects.
Client limits that follow Aave's parameter changes
When a Risk Steward cuts a cap or a reserve is frozen or paused, your limits have to follow the change. Protofire builds a feed of steward updates, freezes and pauses. The feed also records cap usage and the contract revision of each V3 market. For each freeze flag, the feed lists the actions that are still open. The feed records the grace period after a V3 unpause, when liquidations are still blocked.
V4 position managers that the owner can revoke
Your firm's contract can repay or borrow for a V4 position through Aave's built-in Giver, Taker or Config managers. These managers act under allowances that the position's owner grants and can revoke (managers). Protofire prepares the grants for your owner address to sign. We keep a register of each grant and its revocation.
Horizon borrowing and the fund issuer's role
On Horizon, a fund borrower's position is subject to a role that the fund's issuer holds. Protofire handles the allowlist steps with each fund's issuer. We also handle the collateral supply from the qualified address itself. Alerts follow NAV updates, and the feed records each issuer action on the position.
Who decides when an Aave position is frozen, capped or liquidated
Aave's code, Aave's governance and outside liquidators decide what happens to collateral and to new borrows.Protofire's build does not change who makes those decisions. So an Aave position can lose its collateral to a liquidation, stop accepting new borrows or wait on a withdrawal. Each of these outcomes follows rules that Aave and its governance set. Protofire's alerts report when a level that your risk team set is crossed. The alerts do not prevent the crossing.
New assets, new networks, upgrades
Who decides: The Aave DAO, through a forum proposal, a Snapshot poll and then an onchain vote
What your client sees: New markets and upgrades arrive after the vote
Caps, LTV, liquidation threshold and bonus
Who decides: The Risk Steward, "operated by LlamaRisk together with Aave Labs", inside the Aave Risk Framework's bounds. On Horizon, Aave Labs decides in its Executive role (governance)
What your client sees: A cut applies without a vote, and your client limits follow it
Freezing a reserve
Who decides: The Freezing Steward, whose freeze governance alone can reverse. On Horizon, the emergency multisig can also freeze a reserve (Horizon)
What your client sees: New supply and borrows stop at once, but repay and withdraw still work
Pausing the pool or a reserve
Who decides: EMERGENCY_ADMIN, held on V3 by a 4-of-7 emergency multisig
What your client sees: Supply, borrow, repay and withdraw stop together
A liquidation below a health factor of 1
Who decides: An outside liquidator, who on V3 repays part of the debt and takes collateral at a bonus
What your client sees: Collateral goes to the liquidator at a bonus, and your wallet signs no part of it
A Horizon borrower's position
Who decides: The fund's issuer, or a manager it names, holding ATOKEN_ADMIN_ROLE
What your client sees: The issuer can move the position to a new wallet, subject to health-factor checks, and can stop a borrow from growing (tokenization)
As the software developer forgoes its control of the code in favour of the DAO, fixing an operational error, however small, may still require a decision of the DAO.
Our record: lending on Arenas and the Protofire Safe interface
Protofire's record applies to Aave work in two places: lending positions held as aTokens and variable debt tokens, and the signing side.
Arenas and the LandX Credit Gateway
Positions on Arenas use aTokens, variable debt tokens and a health factor. Protofire built the LandX Credit Gateway on Arenas.
BGD Labs' evaluation for Aave names the Protofire Safe interface
BGD Labs, writing as a technical service provider to Aave, said on 15 September 2025 in its evaluation of Aave on Plasma that "an alternative interface for accessing Plasma Safe contracts is the Protofire Safe interface". The evaluation concerns the signing side, meaning the interface that your signers use. Protofire's Safe multisig deployment service has its own page.
How the reader, builder and watcher run
- Step 1
No API key for the reader and the feed
Aave's API takes no key, so your signing keys are the only credentials. The feed books interest from the final block before your cut-off, against the balance at the prior close. - Step 2
The transaction builder runs in your environment
The transaction builder runs in your environment. Each plan reaches the signer that your staff approve. - Step 3
Alert levels and onboarding for each market
Your risk team sets the health-factor levels for each market. V4 manager grants and Horizon onboarding follow the markets that you add. - Step 4
Ownership of the code and the keys
Code that Protofire writes for you is yours by contract, within the license of any third-party software involved. Your wallet or custody platform holds the keys. If you ask Protofire to run the reader and watcher after launch, our managed onchain operations service runs them under a written scope. That scope stops at the reader and the watcher.
How work with Protofire starts
You send your Aave markets (V3, V4 or Horizon), the networks, your signing wallet and the ledger that each position has to reach.The first written proposal ties each market to an Aave contract or API. The terms in this section apply to each phase, as set out on how we work.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When Protofire's Aave work does not fit
In four cases, the work belongs with Aave itself or with another service.
- A ready-made vault is enough. Aave Labs offers Stable Vaults, where "Aave manages the strategies, you integrate the deposit flow". Aave Labs offers them with a sales contact.
- You have one treasury wallet that supplies from a Safe. Aave's own interface covers that case without code.
- You want your own market under your own risk policy instead of Aave's. That is white-label lending, a separate job.
- An issuer wants its own token listed on Aave. Protofire's stablecoin distribution page covers that case.
Protofire holds no key to your wallet and no financial or crypto-asset license. Your firm is responsible for the licensed activity and the client disclosures. Your firm also books a liquidation loss and decides whether to supply or borrow.
FAQ
What is an Aave integration?
Who can build an Aave integration for a fintech, a wallet or a fund?
Who holds the keys to an Aave position?
Can a client withdraw whenever they ask?
Can a Horizon borrower supply fund tokens on a client's behalf?
Does an Aave integration go into a DORA register of information?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
