Crosschain Routing: From Bridge to Finished Position
Introducing Crosschain Routing
Bridges move assets between networks, but moving assets is rarely what users actually want. They bridge because they want to buy an asset, mint a token, enter a vault, provide liquidity, or access an opportunity that lives elsewhere.
Enso Crosschain Routing lets builders attach DeFi actions to the destination side of a bridge. Once the assets land, the route keeps going. Enso can swap them, mint another asset with them, deposit them into a vault, provide liquidity, or push the resulting position into another crosschain step. The bridge becomes an action within a workflow rather than the last step the transaction performs.
From bridging to finished position
With Enso Crosschain Routing, you define what happens after a bridge delivers assets to the destination chain. That could be:
- Bridge an asset and swap it on arrival.
- Move capital to another network and deposit it straight into a vault.
- Bridge to the chain where a minting protocol exists, mint, and bring the result back.
- Move an asset across chains, wrap it, and use it in another protocol.
- Bridge, mint, bridge again, and finish in a yield-generating position.
- Continue through several chains when different parts of a strategy live in different ecosystems.
The end of the route does not have to be a token sitting in the user's wallet. It can be a finished DeFi position.
A crosschain flow, start to finish
Take a stablecoin minted through a protocol on Ethereum, and a user who holds USDC on Berachain and wants to earn yield there. Normally that user bridges USDC to Ethereum, opens the minting protocol, mints the stablecoin, bridges the new asset back to Berachain, and deposits it into a vault. Every one of those is a separate decision point where the flow can break.
With Crosschain Routing, the actions connect:
USDC on Berachain → bridge to Ethereum → mint the stablecoin → bridge back to Berachain → deposit into a yield position
The user starts the route from the source chain. When the USDC arrives on Ethereum, the attached actions continue the workflow. The newly minted asset is bridged back, where another set of actions deposits it into the destination vault.
Products can reach protocols where they actually exist without making the user navigate every network and application in between. For asset issuers, it is also a cheaper distribution model: minting infrastructure stays concentrated on a primary chain while users access the asset from other supported ecosystems.
Under the hood: bridge callbacks
A callback is a set of instructions attached to a bridge action. It tells Enso what to execute on the destination chain once the assets have been delivered. The shape of it:
Source actions → bridge delivery → detect the delivered balance → execute destination actions → optionally bridge again
Described as a route:
Bridge assets to the destination chain
When they arrive:
1. Read the delivered balance
2. Swap or mint using that balance
3. Deposit the resulting asset
4. Optionally continue to another chain
Four details make these workflows reliable in production.
The amount that arrives is the amount that gets used
A destination callback starts by checking the balance of the delivered asset, and that result feeds directly into the next action. The amount detected after delivery becomes the input for the swap, mint, or vault deposit. Nothing has to assume that an exact fixed amount will land.
Destination actions execute together
After delivery, the callback actions run in sequence within the destination transaction, and they succeed or roll back together on that chain.
Source and destination remain separate stages. Crosschain delivery is asynchronous, and a destination failure cannot reverse a bridge that has already finalized on the source chain, so applications should monitor both stages and define receiver and refund behavior. Enso exposes bridge transaction status endpoints, allowing products to track delivery and callback execution.
Callbacks can contain more bridge actions
A bridge can sit inside a destination callback. That gives you nested routes, where the result of one destination operation becomes the input for another bridge. A workflow can move to the chain where an action is available, execute it there, and then continue elsewhere. This is what makes round-trip minting and multi-network yield strategies possible.
Crosschain fees are calculated as part of the route
When a workflow includes destination execution or additional bridge operations, Enso calculates the required fees as part of the parent request. You see the cost of the complete route instead of funding every destination action separately later.
Crosschain protocols
Four are supported today. Chainlink CCIP handles supported ERC-20 transfers and more complex destination instructions. Circle CCTP handles native USDC, with a more limited callback model. Relay covers flexible ERC-20 and native token bridging. Stargate uses LayerZero infrastructure and its supported token pools.
They differ in token support, destination execution, fees, finalization, and callback size. For simple crosschain routes, Enso selects an appropriate path automatically. With the Bundle API, you can name the bridge when a product has specific execution requirements. The integration surface is the same either way.
What this gives products
Wallets can offer direct access to remote swaps, vaults, and DeFi positions, keeping users within the product rather than sending them to a collection of external applications and losing them along the way.
DeFi protocols can take users and capital from other networks. A deposit flow starts with the asset the user already owns and ends inside the protocol's position.
Asset issuers can make an asset accessible across multiple ecosystems without replicating the entire minting infrastructure on every chain.
Fintechs and applications get crosschain execution through a single integration, with their interface, user policies and custody model unchanged. The front end stays simple even when the route behind it crosses several networks and protocols.
Start building with Crosschain Routing.