Use any balance,on any app.

Finch Wallet turns scattered balances and gas into one clear action: choose the app, confirm the outcome, and let the wallet handle the rest.

Try a demo deposit

The live demo uses mock USDC on Base Sepolia and a mocked Hyperliquid bridge on Arbitrum Sepolia. No real funds are used.

Deposit$100into

Hyperliquid.

DEMO INTENT

One confirmation. Finch handles route, gas, and execution in the wallet.

Try this demo deposit

Protocol support

Starting with apps that matter the most.

Finch's architecture doesn't rely on protocol integration. Finch can route into any app's deposit flow on-chain using your account's context.

Hyperliquid mainnet

The same deposit shape, pointed at the real Hyperliquid bridge.

Polymarket

High-inflow USDC deposits are a natural fit for intent routing.

Aave

Supply flows can be wrapped as bounded wallet intents.

Morpho

Vault deposits are composable enough to add without app-side work.

PLANNED

More modules

Planned permissionless modules for more app flows like pump.fun, Lido, Lighter, and Uniswap.

The mismatch

Your balances are everywhere.
Apps expect your wallets
to be perfect.

Cross-chain fundamentals exist, but the experience hasn't caught up. Users manually juggle assets, gas, approvals, and bridges instead of letting wallets compose them.

WALLET REALITY

USDCon Base

spendable, not where the app needs it

USDCon Arbitrum

close, but gas is somewhere else

ETHon Ethereum

valuable, but expensive to move

ETHon Optimism

native gas dust

APP CHECKLIST

1Correct destination chain

2Deposit asset ready

3Native gas available

4Approval and account state set

Before / after

Current wallets make you prepare every step.
Finch handles every step for you.

CURRENT WALLET

01Open destination app

02Connect wallet

03Find the required chain

04Bridge funds into place

05Bridge/Onramp native gas if empty

06Pay fees on each network

07Approve the deposit asset

08Sign each transaction

09Wait for confirmation

Total

~43s

Multiple transactions · multiple fees · native gas required

WITH FINCH

01Choose the app

02Confirm the deposit

03Finch handles gas and routing

Total

~6s

One confirmation · gas handled · wallet-side execution

How it works

A signed order, filled by the fastest solver.

Finch keeps the user flow simple without hiding the safety rails. The wallet signs what is allowed, publishes it, and lets solvers compete to fill it.

Sign the bounds

Your private key signs the order and the exact execution data: asset, amount, destination, fee cap, deadline, and refund address.

Publish on source

The order is created on-chain from the wallet. Solvers can see it, but they cannot change what you signed.

Solvers race to fill

Permissionless solvers compete to execute the destination action first, using whitelisted modules for protocol-specific deposits.

Settle with Wormhole

A Wormhole message proves fulfillment so the source escrow can reimburse the solver.

MEV RESISTANCE

Strict caps, deadlines, and signed execution data limit what a bad fill can extract. Time-priority solver competition rewards fast fills and minimises frontrunning.

Trust layer

The wallet signs the outcome and the limits.

Finch simplifies the flow, but the safety model stays explicit: self-custody, signed orders, whitelisted modules, fee ceilings, deadlines, and refunds.

SIGNED INTENT

deliver $100 USDC → Hyperliquid
fee ≤ $0.01
deadline 60s
refund 0x71C2...9eF2
module Hyperliquid deposit

Self-custodial

Your wallet signs and owns the funds. Finch never takes custody.

Signed orders

Order data and execution data are signed, so a solver cannot tamper with the destination or amount.

Whitelisted modules

Destination actions run through enabled modules, not arbitrary contract calls.

Fee cap

Fees are bounded in the signed order. Above the cap, the intent should not execute.

Deadline and refund

Expired orders stop being fillable, and refunds go back to the signed refund address.

Finch wallet

The wallet is how the abstraction becomes real.

The one-confirmation flow needs EIP-7702-style wallet access, which most existing wallets restrict today. Finch Wallet is built for that path from the start.

BUILT FOR 7702

One confirmation

Sign the outcome once.

Finch Wallet handles the internal authorization, gas, route, and protocol execution behind the deposit intent.

BETTER ROUTES

Cheaper and faster

Solvers compete to fill.

Cross-chain deposits can avoid manual bridges, repeated fee payments, and slow user-side preparation.

COMPOSABLE

No app integration needed

Composability does the work.

If a protocol exposes on-chain deposit actions, Finch can add a whitelisted module and route into it permissionlessly.