
How a new lending market solves the liquidity cold start
Ran Wei, Pharos Network
Moment at 46:08Episode 3 · Credit Markets on Demand
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+.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
Work shipped for 60+ networks and 95+ protocols, including
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.
The firm's Safes hold each power over the market. Protofire writes the code and prepares the transactions those Safes sign.
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:37Which route fits depends on whose rules you need for listings, prices and keys.
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
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
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
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
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.
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.
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.
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.
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.
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.
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.
Protofire built the LandX Credit Gateway on Arenas.
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.
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.
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.
How we work shows a worked proposal.
Three cases call for another route than a market of your own.

Ran Wei, Pharos Network
Moment at 46:08Episode 3 · Credit Markets on Demand
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.