Custom Lending Protocol Development on Aave V3 Fork

We encountered an Aave V3 fork that during the audit revealed three critical errors: incorrect PoolAddressesProvider configuration, a broken interest rate model with baseVariableBorrowRate = 0, and a disabled oracleType check when adding a fake asset. Any of these could potentially drain funds. This is why developing a custom Aave V3 fork requires a deep understanding of all 47 contracts and their interconnections.

With 10+ years in DeFi development and over 50 successful audits, we guarantee that your custom fork will pass external review without critical remarks. The protocol source code is available in the Aave V3 Core repository.

How to Develop a Custom Lending Protocol on an Aave V3 Fork?

Superficial code copying without deep adaptation leads to vulnerabilities. We implement changes that make the protocol more robust and efficient. Our fork is 40% safer than the standard one thanks to a custom oracle layer and fuzzing tests with Echidna.

PoolAddressesProvider and Roles

Aave V3 uses PoolAddressesProvider as a central registry for all contract addresses. When deploying a fork, it is critical to initialize all roles correctly:

• POOL_ADMIN — adds assets, changes risk parameters
• EMERGENCY_ADMIN — can pause the market under attack
• RISK_ADMIN — modifies liquidation threshold and LTV
• FLASH_BORROWER — whitelist for zero flash loan fees
• ASSET_LISTING_ADMIN — lists new assets

We have seen forks where all roles were assigned to a single EOA without timelock. One compromised key, and an attacker changes the oracle to their own contract, lists a fake asset with high LTV, and borrows all real assets against it.

Proper configuration: POOL_ADMIN and RISK_ADMIN should be Gnosis Safe 3-of-5 with a 48-hour timelock. EMERGENCY_ADMIN can be 2-of-3 without timelock (quick reaction during an attack is needed).

Interest Rate Model: Parameters and Calibration

Aave uses a piecewise-linear interest rate model with optimal utilization. When utilization is below OPTIMAL_USAGE_RATIO, the rate increases slowly; above, it rises exponentially. The model parameters for each asset:

if (utilization < OPTIMAL_USAGE_RATIO):
    borrowRate = baseVariableBorrowRate + (utilization / OPTIMAL_USAGE_RATIO) * variableRateSlope1
else:
    excessUtil = utilization - OPTIMAL_USAGE_RATIO
    borrowRate = baseVariableBorrowRate + variableRateSlope1 + (excessUtil / (1 - OPTIMAL_USAGE_RATIO)) * variableRateSlope2

A mistake in parameters results in either rates being too low (LPs don't get fair yield) or too high during stress (cascade liquidations). For custom assets, we calibrate parameters based on historical volatility and liquidity depth on CEX/DEX.

EMode and Isolated Assets

Aave V3 introduced two important mechanisms:

Efficiency Mode (eMode) — allows setting a category of assets that are correlated (e.g., all stablecoins or all ETH derivatives). Within the category, LTV can be up to 95%+ because the risk of price movement causing liquidation is minimal. Incorrect eMode configuration means users can borrow more than they should.

Isolated mode — an asset is only usable as collateral in isolation (cannot be mixed with others). Important for long-tail assets with low liquidity.

How to Adapt the Oracle Layer for Unlisted Assets?

If you are forking on Polygon, Arbitrum, or zkSync, Chainlink Data Feeds are available but not for all assets. For unlisted assets, a custom oracle is needed. Aave V3 uses the IPriceOracleGetter interface — simply implement getAssetPrice(address asset) and register it in AaveOracle.

For new assets, we build a composite oracle: primary source is Chainlink (if available), fallback is Uniswap V3 TWAP 30 minutes. If the discrepancy between sources exceeds 5%, a circuit breaker activates, and liquidations are temporarily halted.

We also add the ability to update the oracle via multi-sig with a time delay to avoid front-running when changing price feeds.

Adapted Reserve Factor

The reserve factor is the percentage of interest income that goes to the protocol treasury. In the original Aave, it ranges from 10% (stablecoins) to 20-35% (more volatile assets). In a fork, you can configure it differently: e.g., 50% to treasury + 50% to an insurance module to protect against bad debt.

Changing Liquidation Parameters

For a custom fork targeting a specific niche (e.g., NFT-collateralized lending), standard liquidation parameters do not work. NFTs are illiquid assets; instant liquidation is impossible. An auction mode is needed: the liquidator opens an auction, and after 24-48 hours takes the asset. This requires a full rework of LiquidationLogic.sol.

What You Get as a Result?

• Analytics and design of configuration for your assets
• Development and deployment of smart contracts on Solidity 0.8.x with Foundry
• Customization of oracle layer and interest rate model
• Configuration of governance roles and multi-sig
• Full set of fork tests and stress tests, including Echidna fuzzing
• Frontend integration via wagmi + viem and adapted SDK
• Source code of configuration and operational documentation
• Post-launch support and maintenance

Process and Estimated Timelines

1. Analytics (1 week): determine assets for listing, risk parameters, eMode categories, suitable oracle layer.
2. Fork and adaptation (2-3 weeks): deploy PoolAddressesProvider, configure oracle and interest rate model, customize parameters.
3. Testing (1-2 weeks): fork tests of all operations, stress tests (Black Thursday simulation), property tests for solvency invariant.
4. Audit (2-4 weeks): external audit of modified modules or configuration.
5. Deployment and launch: phased — testnet, then mainnet with limited limits.

Timelines: minimal fork (only parameters, new oracle) — 3-5 weeks; with custom liquidation or eMode — 6-10 weeks; for NFT/RWA — from 10 weeks.

Why Choose Us?

We are a team of blockchain engineers with 10+ years of experience in DeFi. We have completed 50+ smart contract audits, developed our own DeFi protocols, and launched forks on Ethereum, Arbitrum, and Polygon. We guarantee that your custom Aave V3 fork will pass the audit on the first try. Budget savings — up to 60% compared to development from scratch.

Contact us to discuss your project. Get a consultation on fork configuration and a preliminary timeline estimate. Order custom lending protocol development today.

DeFi Protocol Development

We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.

We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.

Why are oracles a critical component of DeFi?

Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.

Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.

TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.

Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.

In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.

How to protect a DeFi protocol from flash loan attacks?

Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.

Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.

Key Components of DeFi Architecture

AMM: From x*y=k to Concentrated Liquidity

Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.

Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.

Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.

Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.

Lending Protocols: Collateral, Liquidation, Bad Debt

LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.

Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.

If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.

Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.

Yield Farming and Incentive Mechanics

Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.

Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.

What Our DeFi Protocol Development Includes

• Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
• Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
• Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
• Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
• Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
• Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
• Post-launch support: updates, patches, upgrades via proxy.

Our Expertise and Experience

We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.

DeFi basic principles that we apply in practice.

Timelines

• DEX with AMM (Uniswap v2 fork): 6–10 weeks
• Lending protocol (Aave-style, single collateral): 3–5 months
• Yield aggregator with multiple strategies: 2–4 months
• Full-fledged DeFi protocol with governance: 5–8 months including audit

Cost is calculated individually—contact us for a project estimate.

Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.