Liquidity Architecture for MetaMask Integration

How Harbor moves MetaMask from the pioneer of in-wallet swaps to the anchor wallet for in-wallet price discovery.

1. Measuring In-Wallet Swaps Execution

Many in-wallet swaps are serviced by a tangled web of aggregators, intermediaries, and liquidity sources. Often it is not clear how many layers a swap passes through, or even what downstream venue ultimately services the trade. Each hop is an opportunity for value to leak away from the user, usually hand-waved away as "slippage".

1.1 The Liquidity Map: Tracing Liquidity From User to Execution

MetaMask swap trace

Case Study: A BTC -> ETH swap on MetaMask

MetaMask already has strong coverage on in-chain and same-ecosystem routes like USDT -> ETH. Uniswap and the broader EVM liquidity stack cover those pairs well, and MetaMask has spent years making that experience feel simple inside the wallet.

The weak point is newer and structurally harder: swaps between dissimilar chains. TRON USDT -> ETH, BTC -> ETH, and other cross-chain routes that cannot be solved by routing through the mature EVM ecosystem. They require bridging, chain-specific settlement and complex route orchestration. This is where MetaMask, like other cross-chain wallets, are forced into opaque aggregator paths where execution quality starts to break down.

This BTC -> ETH swap exemplifies the challenges users and wallets face when sending flow through aggregators. Though this swap appears to users as a Rango route via Teleswap, it touched 3 different blockchains, and at least as many aggregators or bridges, with fees and time spent at each step. The Polygon/Across legs are not reported by TeleSwap/Rango, meaning fees for this portion are completely obfuscated to the user.

BTC inputBitcoin

BTC tx

TeleSwapVisible route

Rango

Uniswap V3Polygon execution

Polygonscan

Across bridgeOutput bridge

Across

ETH outputEthereum

Etherscan

Quote out vs actual out 0.018551 ETH → 0.018500 ETH ~27.5 bps worse than quote

Fees skimmed (as reported by explorers)

• 0.00000819 BTCBTC UTXO · ~152 bps · MM assumed: 0.00000471 BTC / 87.5 bpsRango/TS assumed: 0.00000348 BTC / ~64.5 bps
• 0.00000038 BTCTeleSwap "Teleporter" Fee · ~7 bps ·
• $0.07Across · ~16 bps ·
• $0.04Ethereum gas · ~9 bps ·
• Estimated total~184 bps

Total elapsed time ~37m 30s Rango reported execution time

1.2 Measuring Execution: Provider EQE Distributions

EQE (Execution Quality, External) measures realized execution against an external reference price. The shape of each provider's distribution shows whether users are consistently landing near CEX reference.

1.3 The Harbor Solution: Two Flows, One Shared Order Book

Regular L1-initiated swaps execute against professional liquidity, while limit orders add a net-new user class: users who are price sensitive, speculative, or willing to set a trade and forget it.

1.3a Swaps Product: L1-Initiated Flow Into Professional Liquidity

The user still starts with a normal MetaMask swap. What changes is the liquidity underneath: Harbor turns that swap into taker flow against a shared order book quoted by professional market makers and other retail limit orders. Instead of relying only on AMMs, RFQs, or intent solvers, MetaMask can route into a transparent market where makers compete on price.

1.3b Limit Order Product: Let Users Name Their Price

The same book unlocks a new order type for MetaMask users: long-lived limit orders. Users leave a buy or sell at the price they want, and it rests on the book until filled. The MetaMask Limit Orders demo shows the full flow: deposit, place a market or limit order, watch it fill, withdraw.

1.3c Why Order Books Beat Intents

Intent and RFQ systems give market makers discretion to execute anywhere between the current market price, the minimum quoted output, and the user's slippage tolerance. A central limit order book removes that discretion. Makers compete in public to fill the order, users receive the best available price. Slippage is a byproduct of the bygone era of constant-product, AMM-based execution. Users should never face 2-3% slippage on major-pair swap, and limit orders directly address it.

2. Harbor Order Book: Compete With CEX

The opportunity

MetaMask Swaps does roughly $250M/mo¹ today. Binance does roughly $550B/mo in spot volume⁴. That means MetaMask routes about 0.045% of what a single CEX moves, despite a large wallet user base. The gap is market structure: CEX users get live books, limit orders, and competitive maker pricing; wallet users mostly get aggregator routes.

Harbor brings the CEX primitive into the wallet. A MetaMask user placing a BTC/USDT limit order should be able to get Binance-grade execution without leaving MetaMask.

2.2 Order Book Volume & Fee Projections

The sizing question is how much active major-pair trading can stay inside MetaMask once users have CEX-style execution.

Power-law distribution used as a proxy. Replace with MetaMask's actual swap-volume-by-token breakdown for precise comparison.

MetaMask has meaningful exchange-scale reach, but without an order book it cannot capture the active trading behavior that still lives on CEXs.

Key insight: closing just 0.1% of the major-pair gap adds ~$360M/mo, more than MetaMask's entire public swap volume today. At 0.5%, the order book adds ~$1.8B/mo of new volume.

3. Proposed Roadmap

This is the proposed feature integration and product development path for the Harbor <> MetaMask partnership.