Wallets and aggregators integrate a DeFi protocol when it adds volume or yield and costs their engineers almost nothing. So do the work for them. Publish a DefiLlama adapter, expose a standard quote or deposit function, and serve live data. Then pitch the numbers to the one product owner who decides.

Why do wallets and aggregators control distribution?

Most users never pick a protocol. They tap "swap" or "earn" in a wallet, and the wallet or its aggregator picks for them.

DefiLlama tracked 190 DEX aggregators that routed $73.1B of trades in the 30 days to 14 October 2026 (DefiLlama aggregators). That is about 25% of the $290.6B traded on DEXs (DefiLlama DEXs). The ratio is our arithmetic, and some aggregator volume also counts as DEX volume.

A few teams hold the routing. The five largest aggregators handled 61% of that volume, and the top ten handled 84% (our arithmetic on the same data). A protocol inside the ten largest routers reaches most aggregated flow on their chains.

Wallets also earn from these choices. Seven self-custody wallets took $12.2M in fees in the same 30 days (DefiLlama fees). A wallet weighs each integration against that revenue, and against support tickets from users who lose money.

Who makes the integration decision?

Each partner type has a different owner and a different need:

  • DEX aggregator. An integration engineer decides, with a BD lead for priority. They need a callable quote function, gas costs and test pairs.
  • Yield aggregator. A strategist decides. They need deposit and withdraw functions, reward data and exit liquidity.
  • Wallet swap screen. The swaps product manager decides. They need better fills than the current default, measured per pair.
  • Wallet earn screen. The earn product manager decides, with risk or legal review. They need a one-step deposit, a clear withdrawal time and contract control details.
  • Data sites. Maintainers of public adapter repos decide. They need adapter code computed from chain data.

The usual blockers are unreliable quotes, high gas, rewards that end soon and withdrawal queues. For swap venues, see how prop AMMs change where on-chain order flow goes.

What should you ship before the first conversation?

Ship what lets a partner test you without a meeting. Work in this order:

  1. List on DefiLlama. Fork the adapters repo, compute TVL from chain data, and open a pull request (DefiLlama docs).
  2. Get your pools into DefiLlama yield data. Separate base yield from token rewards.
  3. Publish a standard quote function, or standard deposit and withdraw functions with no custom approvals.
  4. Open a pull request, with passing tests, to each target router or vault repo.
  5. Serve live rates, depth, utilisation and withdrawal times through an API.

Add a one-page control sheet for the earn team's risk review: admin keys, timelock, audits and incident contact.

Partners check DefiLlama first, and its queue moves fast. 459 pull requests merged into the adapters repo in the 30 days to 14 October 2026, with 28 open on that date (GitHub).

That day, DefiLlama's yield service listed 16,843 pools from 501 projects, and 2,745 held $1M or more (DefiLlama yields). The $1M count is our arithmetic. A strategist compares you against that list.

How do you pitch once the code is ready?

Pitch a number the product owner can check on their own screen:

  • Aggregator: the share of test swaps on your top pairs where your quote beat their route, with the date range.
  • Wallet: the yield, the withdrawal time and the fee income their users would generate, at today's rates.

Reach people where they already work. Integration engineers live in GitHub issues and developer chats. Wallet product managers announce new chains and earn products in public, and each announcement opens a short window when they need protocols.

Market share follows integrations. We took FastLane from 10% to 75% market share before Chainlink acquired the engine. See how blockchain infrastructure protocols grow market share.

How long does an integration take?

Code-first integrations move fastest. We sampled 100 adapter pull requests merged in the 30 days to 14 October 2026. The median time to merge was 11 hours, and 93 merged within three days (our arithmetic on GitHub data).

Router repos set their own pace, so ask each maintainer. A wallet earn screen takes longer, because it adds risk review and, in some regions, legal review. Plan around the slowest partner, and start it first.

What is the decision rule?

If a partner needs more than a day of engineering to test you, do that work yourself before you ask for a call. Then check:

  • DefiLlama adapter merged and TVL method published.
  • Yield pools listed, with base and reward APY separated.
  • Quote, deposit and withdraw functions documented, with test cases.
  • Pull requests open to the ten routers or vault platforms with the most volume on your chain.
  • One dated proof point per partner type, and wallet owners mapped to their launches.

To see the routers, vault platforms and wallets that fit your protocol now, start with five named buyers, free, each with a dated reason.