Skip to content

Onchain White-Label Lending on an Aave V3 Fork Your Firm Owns

Protofire builds white-label lending markets on a fork of Aave V3 for chains, fintechs, RWA issuers and credit funds. Each firm chooses its own collateral list, price feeds and liquidators, and its Safes hold the admin roles. We deployed Safe on 120+ EVM networks, where it secures $2B+.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Your firm's jobs
  3. Ways to add lending
  4. What you get
  5. Roles and keys
  6. Why Protofire
  7. How the build runs
  8. How work starts
  9. Not the right fit
  10. Related guides and services
  11. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

White-label lending under your brand and your rules

White-label lending puts a lending market under your brand and your rules. You have a credit policy, a collateral list and borrowers you have approved, and a public lending protocol follows none of them.

Protofire builds the market as a fork of Aave V3, and your Safes hold the keys. The code is the easy part. The jobs around the code decide whether the market works.

Who builds and who holds each part of a forked Aave V3 market

The firm's Safes hold each power over the market. Protofire writes the code and prepares the transactions those Safes sign.

The firm and its Safes

Brand, onboarding and lending policy

These are the firm's product, onboarding records, collateral list, deficit rule and named liquidators.

Owner timelock

The timelock owns the PoolAddressesProvider, behind a delay that users can read onchain.

Risk and emergency roles

RISK_ADMIN, ASSET_LISTING_ADMIN and EMERGENCY_ADMIN control caps, LTV, listings and freezes.
Outside parties

Aave V3 contracts

The Pool, ACLManager, AaveOracle and tokens are copied from the release that the proposal names.

Price sources

Prices come from market feeds or from a NAV that the issuer publishes.
Protofire builds

Deployment scripts and activation payload

The scripts hand each role to your Safes, and your Safe signs the payload that switches the market on.

Allowlist checks and price adapters

Allowlist checks run in the forked Pool, and each price has bounds and a maximum age.

Liquidation bot

Your staff put the bot into production, and the bot signs with your key.

Branded app and indexer

Protofire builds the app, a subgraph of positions and role changes, and alerts.

Jobs your firm takes on when it owns the market

On a fork, your firm does the jobs that Aave's governance does for its own markets: listing, pricing, liquidation and keys.

On a fork, a price adapter must apply bounds and a maximum age that your risk owners set. Aave's oracle contract reads no timestamp, so a stale price passes through (AaveOracle.sol). For example, take a tokenized fund as collateral. Its price is a NAV that the issuer publishes on its own schedule. On Aave's Horizon instance, a NAV that breaks preset bounds never reaches the protocol, and the oracle holds the previous accepted value (Horizon).

A market also needs someone to liquidate. If the collateral token moves only between allowlisted wallets, a liquidator outside that list cannot receive the token. The list must also admit the aToken contract, which holds every supplied unit. If no liquidator is named, the position remains under water and its debt keeps growing. Your emergency Safe can freeze the reserve. A freeze stops new supply and borrows, while repay and withdraw still work (Aave docs).

Losses need an owner too. Later V3 releases book the debt of an account left with no collateral to the reserve as a deficit. Only the address registered as Umbrella can reduce that deficit. On a fork with that feature, your Safe picks the Umbrella address, such as a first-loss buffer that you fund. Until a deficit is covered, aToken balances keep their full value, so your documents must say who absorbs the rest.

The law differs by region. MiCA leaves the lending and borrowing of crypto-assets outside its scope. In January 2025 the EBA and ESMA wrote that some of these activities "may fall under provisions in existing national financial services law". Your counsel decides what authorization each country needs.

Ran Wei described how RWAs differ from native crypto assets as collateral in Protofire's Protocol Roundtable episode on credit markets on demand.

[...] using RWA as a collateral is slightly different from, you know, native crypto assets. For example, like, sometimes they don't have a DEX liquidity, and also some of the RWAs, they don't really have an oracle price feed.
Ran Wei, Head of DeFi, Pharos Network · The Protocol Roundtable by Protofire, Episode 3, 14:37

Three ways to add lending to your product

Which route fits depends on whose rules you need for listings, prices and keys.

Fits when

Connect to a public market: Your customers can use markets that others list and govern, on Aave or Morpho

Instance under Aave's framework: You want Aave liquidity or the DAO's providers to deploy, and you accept terms that a governance vote sets

A fork your firm owns: You need your own collateral list, holder rules, deficit rules and admin keys

Who lists and sets risk

Connect to a public market: Aave's governance on Aave. On Morpho, market creators and vault curators

Instance under Aave's framework: The instance's owner, under terms that the Aave DAO approves

A fork your firm owns: Your risk owners, through their Safe

Who deploys

Connect to a public market: Nobody, because the markets already run

Instance under Aave's framework: "Aave DAO and Service Providers will handle deployment"

A fork your firm owns: Protofire prepares the scripts, and your deployer key and Safes sign them

Code license

Connect to a public market: None, because you copy no code

Instance under Aave's framework: A license from the Aave DAO under its framework, passed 11 November 2024

A fork your firm owns: The license of the release that the fork copies

What you get from a white-label lending market

Deployment scripts that hand each role to your Safes

Protofire prepares the deployment scripts, first on a testnet. The contracts are created from a deployer key that you hold. The same script hands ownership and each role to your Safes and revokes the deployer's roles. The market is inactive until your Safe switches it on, after your risk team has read each role onchain.

Only people you have onboarded can open a position

Protofire builds allowlist checks inside the forked Pool and on aToken transfers. The checks take their list from your onboarding records. A removed address can still repay, withdraw and be liquidated, but it cannot open anything new. A borrow-only setup lets only your own users draw.

Price sources and a listing file for each collateral

Before an asset is listed, your risk owners see the source, bounds and maximum age of its price. Protofire builds the oracle configuration and a listing file. The listing file proposes LTV, liquidation threshold, bonus and caps. Illiquid collateral gets its own isolation in the file. Protofire's oracle integration service covers feeds beyond this market.

A named liquidator when the market opens

You decide who liquidates. Each liquidator you name needs capital to repay and a written way out of the seized collateral, such as redemption with the issuer. As an option, Protofire writes the liquidation bot. Your staff put each release of the bot into production. The bot signs with your key from hosts closed to Protofire.

A branded app, a subgraph and alerts

Protofire builds the app in your brand, a subgraph, and alerts for stale prices and parameter changes. Your team sees each position and each role change. After launch, we can run the indexer read-only under a written scope, as monitoring of the market's contracts in production.

Who holds the keys to a market Protofire builds

Your Safes hold ownership of the market and each of its roles from deployment.Aave V3 gives one owner the power to swap a market's code. Aave V3 records every other power as a role in the ACLManager. Each power acts behind a delay that you set before launch, and the emergency role has no delay.

Our record: LandX Credit Gateway, Tezos lending and Safe

Protofire's record covers a credit gateway, lending and borrowing on Tezos, and the Safes that hold the roles of a market like this one.

The LandX Credit Gateway on Arenas

Protofire built the LandX Credit Gateway on Arenas.

Tezos Foundation grants for a liquidity pool, then lending

In 2019 the Tezos Foundation granted Protofire funds to build a Tezos liquidity-pool contract with a demo client and tutorials. Later, the Foundation granted Protofire funds to add lending and borrowing. This Tezos work is in the past.

Safes that hold a lending market's roles

Protofire deployed Safe on 120+ EVM networks, where it secures $2B+. In a May 2026 post, the Safe Ecosystem Foundation says Protofire "has been contributing to Safe since 2018". A market's owner and risk roles raise one question: who must agree before a parameter changes. A Safe answers that question. Protofire's Safe multisig deployment page gives the details.

How the market build with Protofire runs

  1. Step 1

    Review of your collateral, price publishers and Safes

    An engineer reads your collateral, price publishers and Safe layout. A written proposal follows, and it names the Aave release that the fork copies.
  2. Step 2

    Deployment of the fork on a testnet

    Protofire deploys the chosen release with the allowlist checks, the price adapters and the listing file. Your risk team reads the owner and each role onchain. Your auditor receives Protofire's changes.
  3. Step 3

    Activation by your Safe

    The activation payload waits for your Safe to execute it. Until your Safe executes the payload, the market is inactive.
  4. Step 4

    Upgrades that your Safe signs

    A later upgrade of the Pool reaches the market only when your Safe signs it. Protofire can prepare an upgrade together with its tests.

How work with Protofire starts

Work with Protofire starts when you send the collateral you plan to list and the chain.You also tell us who publishes each price and which Safe addresses will hold ownership and each role. The first written proposal scopes the fork, the allowlist checks, the price adapters and the app. If you take the liquidation bot, the proposal scopes it too. Your counsel reviews the license of the chosen release and decides whether it suits your use. The how we work page sets the terms for each phase that follows.

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 a lending market of your own does not fit

Three cases call for another route than a market of your own.

  • The asset is not tokenized yet. See issuing the token a market lends against.
  • A bank lends fiat against a client's crypto inside its own books. Protofire's crypto-backed credit blueprint covers that model.
  • You want Protofire to list assets, post prices or liquidate positions after launch. Protofire holds no role in the market and does none of these three jobs.

FAQ

What is white-label lending onchain?
White-label lending onchain is a lending or private credit market that a firm deploys from a protocol's code and then owns, brands and governs itself. Protofire builds the Aave V3 fork and the allowlist checks for such a market. We also build the price adapters and the app. The firm's Safe holds the upgrade path and each admin role. The firm's risk owners choose the collateral and the price sources.
Who can build a white-label lending market for a fintech, an RWA issuer or a credit fund?
Protofire builds white-label lending markets on a fork of Aave V3 and shapes each one to the firm. A fintech gets a borrow-only market for its app users. That market breaks when the allowlist and the app's onboarding records no longer match. An RWA issuer gets its token, NAV feed and named liquidators listed, and the token's transfer rules must admit those liquidators. A credit fund gets a permissioned pool for its own lenders and borrowers, and a written rule says who absorbs a deficit. A chain gets a flagship market.
Which Aave code may a firm's own market run in production?
The license of the Aave release that a market copies decides which code it may run in production. The original Aave V3 code has been under the MIT license since 27 January 2023 at the latest. Later V3 releases are under a Business Source License until 6 March 2027 at the latest. The use grant of that license excludes anyone who deployed a competing fork in production in the preceding four years. The Aave DAO can waive that exclusion. Aave V4 allows production use only under a waiver or a commercial license until its change date.
Do Aave's security fixes reach a forked market?
No, Aave's security fixes do not reach a forked market by themselves. A fork runs the code it was deployed with. A new Pool implementation reaches the fork only when your Safe signs the change. Protofire's allowlist checks change Aave's code, so each upgrade includes those changes and goes back to the auditor. Aave's releases also change behavior. Later V3 releases removed Isolation Mode and Siloed Borrowing, so your firm decides whether to follow.
Who audits the market before launch?
An independent audit firm audits the market before launch. The client appoints that firm and contracts with it directly. Protofire's changes to the Aave code go to that firm, together with the release they modify and Protofire's tests. We fix the findings before your Safe signs the activation payload.
Can a borrower draw without posting collateral?
A borrower can draw without posting collateral only through credit delegation, which the fork keeps from Aave V3. Protofire's allowlist checks admit only delegates that you have onboarded. A supplier approves the borrower, and the debt is recorded in the supplier's position. A draw beyond the supplier's borrowing power reverts. Aave's docs leave the terms to "offchain via legal agreements or onchain via smart contracts", so your credit documents state them.
Which Annex III service type covers building a lending market?
Building a lending market is Annex III type S02, "ICT Development". That type applies when an EU financial entity records Protofire's build among its DORA third-party arrangements (Regulation 2024/2956). Running the indexer would add type S14. Your compliance and legal owners decide what is filed. Protofire's DORA guide sets out the types.

Discussed on The Protocol Roundtable

All episodes

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.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.