> For the complete documentation index, see [llms.txt](https://web3-news.gitbook.io/universal-bridge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://web3-news.gitbook.io/universal-bridge/universal-bridge-what-it-is-and-how-it-works.md).
# Universal Bridge: What It Is and How It Works
Universal Bridge is a developer-facing cross-chain routing layer for EVM apps. It lets a user pay, swap, bridge, or onramp with an asset on one network while the app receives the requested asset on another. The product combines route selection, transaction preparation, and status handling behind a unified interface; it is not a new blockchain or bridge standard.
### Universal Bridge turns a fragmented task into one request
Most blockchain applications are tied to the chain where they were deployed. A user may hold USDC on Ethereum, need ETH on Base, and have no native ETH available to pay the transaction fee. Solving that manually can require a token approval, a swap, a bridge transfer, a network change, and several wallet signatures.
Universal Bridge is designed to combine those steps. The developer describes the desired outcome: buy a certain token on a destination chain, sell one asset for another, transfer funds, or purchase crypto through an onramp. The system then searches for a workable route and returns the transactions needed to complete it.
That is an orchestration role. It does not mean every asset is placed inside one universal token contract, and it does not mean the product replaces protocols such as Uniswap, Across, Axelar, LayerZero, or Hop. It gives an application one interface for reaching the underlying liquidity and interoperability systems.
### Three user outcomes explain the product's job
The practical functions fall into three groups:
* **Buy:** receive a specified token on a specified chain, using another token or a fiat payment method.
* **Sell:** convert an asset into a requested token, potentially across networks.
* **Transfer:** move an asset to another wallet or chain without asking the user to assemble the route manually.
An onramp is the fiat-to-crypto part of that flow. A user might pay with a card or another supported payment method while the recipient receives an on-chain asset. A swap changes one token for another, while a bridge moves value or a representation of value between blockchain environments.
The distinction matters. A normal bridge may only move ETH from Ethereum to Arbitrum. A routed transaction could instead swap USDC for ETH, use a liquidity network to cross to another chain, and deliver the result to the recipient. Ethereum's [blockchain bridge overview](https://ethereum.org/bridges) describes bridges as connectors between otherwise separate blockchain ecosystems.
### The route decides whether value is bridged, swapped, or both
There is no single bridge mechanism behind every cross-chain transaction. Ethereum's technical guide identifies three common designs: lock-and-mint, burn-and-mint, and atomic swaps. It also distinguishes native bridges, validator or oracle-based bridges, generalized message-passing systems, and liquidity networks. The same guide notes that fees can vary with gas costs and the liquidity available on a route.
Universal Bridge sits above those mechanisms. It can select a path based on the origin chain, destination chain, token addresses, amount, wallet addresses, and available route constraints. A route may involve a DEX such as Uniswap on one chain, a bridge or liquidity protocol between chains, and a second swap before the destination transfer.
That makes the product closer to a router and adapter layer than to a standalone bridge network. The important output is not a new wrapped token or a new consensus system. It is a prepared sequence of calls that a wallet can review and sign.
thirdweb describes the design in its [private-beta documentation](https://portal.thirdweb.com/changelog/universal-bridge-private-beta):
> “Universal Bridge uses a combination of existing protocols and onramps with thirdweb's own onchain and off-chain infrastructure for maximum coverage and reliability.”
### Gas and liquidity charges stay chain-dependent
A route does not have one universal fee. The total cost can include source-chain gas, destination-chain gas, bridge or relayer charges, DEX fees, price impact, and any fee charged by an onramp or application. Gas means the fee paid for transactions and smart-contract execution on a blockchain, as defined by the [Ethereum glossary](https://ethereum.org/glossary).
On EIP-1559-compatible EVM networks, the network component is generally expressed through a base fee and a priority fee. A multi-step route can require several transactions, so the user should inspect the quoted output, the expected amount received, and the number of approvals before signing.
Liquidity also affects the result. A large swap against a shallow automated market maker pool can produce more price impact than a smaller swap. A bridge route may be fast but expensive, while another may be cheaper but depend on slower settlement or less available liquidity. The strongest route is therefore not always the one with the lowest visible fee.
### The main trade-off is convenience versus inherited risk
The advantage is clear: users do not need to understand every intermediate protocol, and developers do not need to build separate integrations for every chain, swap venue, bridge, and fiat provider. The product can present a single flow inside an app, reducing network switching and abandoned transactions.
The trade-off is that routing does not erase the risks of the systems it calls. Smart-contract bugs, incorrect token addresses, bridge failures, liquidity shortages, oracle errors, compromised validators, and onramp restrictions can still affect a transaction. Ethereum's bridge guidance classifies these as material risks and emphasizes that security, speed, connectivity, and cost involve trade-offs.
Users should verify the destination chain, token contract, recipient address, minimum received amount, expiry, and requested wallet approvals. Developers should also surface route status and failure states instead of treating a prepared quote as proof that settlement has completed.
### For builders, the useful asset is the interface
The developer-facing model is intent-based. In the .NET and Unity integration, the documented examples expose methods for buy quotes, prepared buys, sell quotes, prepared sells, transfers, status checks, and managed execution. A prepared request returns the transactions required for the route, which the wallet can execute sequentially.
The same integration shows a concrete example: USDC on Ethereum is used to obtain ETH on zkSync. The code separates the quote from the executable transaction set, allowing an application to show an estimate before asking the user to sign. The documentation is available in the [Universal Bridge integration reference](https://portal.thirdweb.com/changelog/net-unity-universal-bridge-integration).
At its March 20, 2025 private-beta announcement, thirdweb said the service supported more than 30,000 routes across more than 50 chains. That is a historical product claim, not a guarantee of today's availability; supported assets, route quality, fees, and execution times should be checked for the exact transaction.
For readers who want the product's cross-chain routing and payment overview, the [Universal Bridge overview and access page](https://universal-bridge.net/) is the relevant next stop. The central answer remains simple: Universal Bridge is an abstraction layer that turns a user's cross-chain goal into a route, a quote, and executable blockchain transactions.
### Questions readers still ask
#### Is Universal Bridge a blockchain?
No. It is a cross-chain routing and transaction interface for applications using EVM-compatible networks.
#### Does it only move the same token?
No. A route can combine swaps, bridge transfers, and onramps to deliver a different token on the destination chain.
#### Who pays the gas fees?
The wallet or payment flow pays the network fees required by the transactions in the selected route.
#### Is every route equally safe?
No. Risk depends on the chains, smart contracts, bridges, liquidity providers, and payment services used by that route.
#### Where should supported chains and fees be checked?
The current route, asset, fee, and execution details should be checked on the [Universal Bridge](https://universal-bridge.net/) page before signing.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://web3-news.gitbook.io/universal-bridge/universal-bridge-what-it-is-and-how-it-works.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.