---
name: avax-defi
description: Integrate Avalanche exchanges and lending protocols using version-matched deployments and executable quotes.
---

# Avalanche DeFi integrations

Source review: 2026-09-06. Recheck network-dependent facts before use.

1. Define the required primitive—swap, liquidity position, supply, borrow or liquidation—and the target chain. Select an actual deployed protocol from official documentation; use [Addresses](../addresses/SKILL.md) to resolve each contract.
2. Match the ABI and economic model to the protocol version. LFJ Liquidity Book uses its own router/path and bin model; an Ethereum Uniswap example is not a drop-in integration. Its V2.2 paths and hook behavior must be checked against that version.
3. For lending, identify the specific Aave market and live reserve configuration. Check the operation's enabled/paused state, caps, collateral settings and account health from contracts. A protocol's presence on Avalanche does not make every asset borrowable.
4. Quote the exact size and route. Distinguish indicative analytics prices from executable output. Bind minimum received, deadline where supported, recipient, token identities and spender to the user's intent.
5. Fork-test the live integration and measure input/output balance deltas. Exercise unavailable liquidity, price movement, token decimals, fee behavior and stale quotes. Show net results with actual gas and protocol fees, not gross quoted returns.

**Evidence to return:** versioned deployment manifest, quote timestamp/block, bounded execution parameters, simulation/fork results and realized deltas when execution was authorized. Ecosystem coverage here is a starting set, not an endorsement or exhaustive market ranking.

## Primary sources

- [LFJ Avalanche deployments](https://developers.lfj.gg/deployment-addresses/avalanche)
- [LFJ V2.2 changes](https://developers.lfj.gg/key-changes)
- [Aave network deployments](https://aave.com/help/aave-101/accessing-aave)

## Choose a demonstrated recipe

| Recipe | Executed local-fork path | Key distinction |
| --- | --- | --- |
| [Pharaoh](../pharaoh/SKILL.md) | Current CL WAVAX→USDC | int24 tickSpacing; xPHAR/DLMM separate |
| [LFJ](../lfj/SKILL.md) | LBv2.2 WAVAX→USDC | V2_2=3; zero leftover input |
| [Blackhole](../blackhole/SKILL.md) | RouterV2 AlgebraV2 swap | Six-field route/final receiver/helper proxy |
| [Aave V4](../aave-v4/SKILL.md) | Main/tokenized USDC supply and withdrawal | Hub/Spoke IDs, not V3 aTokens |
| [Silo](../silo/SKILL.md) | Market103 deposit/withdraw | Explicit collateral mode and paired debt |
| [Euler](../euler/SKILL.md) | Selected EVK deposit/withdraw | EVC risk graph/caps/deprecation |
| [BENQI](../benqi/SKILL.md) | Core supply/redeem, sAVAX stake/unlock | Return errors and asynchronous exits |

From the complete bundle root run `node --test examples/protocols/*/recipe.test.mjs`, then each family's live/fork runner. All modules expose manifest/inspect/plan, but schemas differ: DEX action swap, Aave/BENQI named operation, Silo/Euler account/market context. Do not invent one common ABI.

Silo/Euler funded borrowing and mature sAVAX redemption remain unproved successful paths. LP management, governance/claims, leverage and liquidation require further exact interfaces/stateful verification. For compositions trace every spender/callback, raw unit, fee and net outcome. A spot spread or APR is not executable profit or risk evidence.