Cross-Chain Bridge
Overview
OHM is available on more than one chain. Olympus moves native OHM between the supported chains. Each chain has one OHM token, and the bridge does not issue a separate bridge token. Thus, the OHM that you receive on a chain is composable with every dApp on that chain.
All bridge lanes use Chainlink CCIP (Cross-Chain Interoperability Protocol). Each chain has a CCIP token pool that holds the OHM accounting for that chain:
- On Ethereum, the token pool locks OHM when it leaves Ethereum and releases OHM when it returns.
- On Arbitrum, Optimism, Base, Berachain, Robinhood Chain and Solana, the token pool burns OHM when it leaves the chain and mints OHM when it arrives.
Ethereum is the canonical chain for OHM. Only Ethereum can mint net-new protocol OHM. The OHM on every other chain is backed by OHM that is locked in the Ethereum token pool. The totalSupply of OHM on Ethereum includes the OHM in this pool. Thus, to calculate the OHM supply on all chains, add the supply of each chain, then subtract the OHM in the Ethereum token pool. A completed bridge transfer does not change this value.
The CCIP lanes between Ethereum and Solana were already in operation before the rollout to the other chains. The CCIP lanes to Arbitrum, Optimism, Base, Berachain and Robinhood Chain opened on November 3, 2026, after the execution of OCG proposal 19.
For the architecture, the access control, the rate limits and the emergency controls, refer to Cross-Chain Bridge: Technical Details.
How to bridge
- Go to the Bridge page.
- Connect your wallet.
- Select the source chain and the destination chain.
- Enter the amount.
- If the app asks for an approval, click Approve OHM for Bridging.
- Click Bridge OHM.
- Find the transfer in the Transactions list.
The Transactions list shows the status of each transfer and a link to the CCIP Explorer. It also shows your earlier transfers through the LayerZero bridge. You can also find a message in the CCIP Explorer with its message ID or its transaction hash. If a transfer has the status Needs Retry or Needs Recovery, refer to Failed messages.
Olympus does not charge a fee for bridging. You pay the gas on the source chain and the CCIP fee in the native token of the source chain.
The time for a transfer depends on the finality of the source chain. The CCIP Explorer shows the status of each transfer.
The app checks the rate limits of the route before you send. If the amount is more than the route can pass now, the app shows Exceeds Route Limit. In this case, send a smaller amount, or wait until the limit refills.
For a transfer to Ethereum, the app shows Exceeds Available Liquidity if the Ethereum token pool holds less OHM than the amount. In this case, send a smaller amount, or wait until the pool holds more OHM. A refill of the rate limit does not add OHM to the pool.
If you use a Safe, the app shows Propose in Safe instead of Bridge OHM. The other signers then confirm the transaction in the Safe app. A contract wallet can have no code at the same address on the destination chain. In this case, the app asks for a recipient. Enter an address that you control on the destination chain.
The Bridge page does not support Solana yet. To bridge between Ethereum and Solana, send the transfer through CCIP directly. On Ethereum, you can call sendToSVM on CCIPCrossChainBridge.
The recipient wallet on Solana must have an OHM associated token account before the transfer arrives. CCIP does not create this account. If the account does not exist, the transfer fails on Solana. To complete the transfer, create the account. Then execute the message manually from the CCIP Explorer.
Supported networks
Ethereum, Arbitrum, Optimism, Base, Berachain, Robinhood Chain and Solana. The Bridge page supports all of these networks, except Solana.
Bridge lanes
Each line in the diagram is a lane that operates in the two directions. Ethereum connects to every chain. Arbitrum and Base connect to every EVM chain.
| From / To | Ethereum | Arbitrum | Optimism | Base | Berachain | Robinhood Chain | Solana |
|---|---|---|---|---|---|---|---|
| Ethereum | - | Yes | Yes | Yes | Yes | Yes | Yes |
| Arbitrum | Yes | - | Yes | Yes | Yes | Yes | No |
| Optimism | Yes | Yes | - | Yes | No | No | No |
| Base | Yes | Yes | Yes | - | Yes | Yes | No |
| Berachain | Yes | Yes | No | Yes | - | No | No |
| Robinhood Chain | Yes | Yes | No | Yes | No | - | No |
| Solana | Yes | No | No | No | No | No | - |
The mechanism of a lane depends on the source and the destination:
| Lane | Mechanism |
|---|---|
| Ethereum → other chain | OHM is locked in the Ethereum token pool. Native OHM is minted on the destination chain. |
| Other chain → Ethereum | OHM is burned on the source chain. OHM is released from the Ethereum token pool. |
| Between two chains other than Ethereum | OHM is burned on the source chain and minted on the destination chain. The Ethereum pool does not change. |
Chainlink has no lane between Optimism and Berachain, between Optimism and Robinhood Chain, or between Berachain and Robinhood Chain. To move OHM between these chains, bridge through Arbitrum, Base or Ethereum.
The lanes between Solana and the other chains (not Ethereum) were not part of the rollout. The DAO can add the EVM side of each lane later, through the configuration timelock of the chain. Olympus does not hold a role on the Solana token pool. Thus, the owner of the Solana token pool must add the Solana side. Until both sides are added, to move OHM between Solana and one of these chains, bridge through Ethereum.
Migration from the LayerZero bridge
Before CCIP, the OHM on Arbitrum, Optimism, Base and Berachain came from the LayerZero CrossChainBridge. That bridge is closed. The CrossChainBridge policy is deactivated on Ethereum, Arbitrum, Optimism, Base and Berachain.
You do not need to do anything with your OHM. The OHM token address on each chain did not change, and your OHM stays valid. Your earlier LayerZero transfers stay visible in the Transactions list of the Bridge page.
Before the OCG proposal, the DAO Multisig deposited OHM into the Ethereum token pool. The deposit backed the OHM supply on Arbitrum, Optimism, Base and Berachain at that time (approximately 130,721 OHM). Thus, the pool can release OHM on Ethereum for all of the OHM that the LayerZero bridge minted on those chains.
Robinhood Chain is new to Olympus. The LayerZero bridge did not serve it. Its OHM token started with a supply of zero, and all of its OHM arrives through CCIP. Thus, Robinhood Chain did not increase the deposit.
Security
What "native" means
Bridge exploits caused approximately half of all the funds lost in DeFi exploits.
The Olympus bridge uses lock-and-mint accounting between Ethereum and the other chains. This is the same mechanism that many bridges use. The difference is the issuer of the token on the destination chain:
- A typical bridge issues its own wrapped token. The bridge operator controls that token, and each bridge creates a different representation of the same asset.
- On Arbitrum, Optimism, Base, Berachain and Robinhood Chain, OHM is an Olympus token. Only the Olympus Kernel of that chain can mint it, through the
MINTRmodule. Each chain has one OHM token, and all bridge transfers use it.
Thus, Olympus can change the bridge provider and keep the token. For example, the OHM token addresses on the EVM chains do not change in the move from LayerZero to CCIP.
On Solana, the CCIP token pool and its owner are Chainlink contracts. Olympus does not hold a role on the Solana pool.
The Ethereum token pool
The Ethereum token pool holds the OHM that backs every other chain. Thus, like the lock contract of any lock-and-mint bridge, it is a concentration of value. The guardrails that follow limit the risk to the pool.
Guardrails
- Supply bound. OHM can return to Ethereum only from the Ethereum token pool. If an attacker mints OHM on another chain, the amount that can return to Ethereum is limited to the OHM in the pool. The bridge cannot mint new OHM on Ethereum.
- Release limit. Only a verified CCIP message can release OHM from the pool. The inbound rate limit of each route also limits how fast the pool can release OHM. In an incident, the Emergency Multisig can stop all routes immediately, and an OCG proposal can withdraw OHM from the pool.
- Rate limits. Each route has an outbound limit and an inbound limit on each side. Each limit is a token bucket with a capacity and a refill rate, not a daily cap. An empty bucket refills completely in 24 hours. Thus, a full bucket can pass approximately two times its capacity in 24 hours. A limit stops a large or sudden flow, also if a different control fails. Refer to Rate limits.
- Message verification. The Chainlink decentralized oracle network verifies each CCIP message. The independent Risk Management Network can also stop a lane.
- Timelock on configuration. On Ethereum, the DAO Multisig queues route and rate-limit changes on a timelock. A change can execute only after a delay of 1 day. Each queued change is visible on-chain, and the Emergency Multisig can cancel it. On the other EVM chains, there is no OCG. The local DAO Multisig holds the
adminrole there, and it can change routes and rate limits directly, without the delay. - Governance ownership. On Ethereum, the Olympus on-chain governance (OCG) timelock holds the
adminrole, the OHM administrator role in the Chainlink registry, and the rebalancer role of the pool. These roles control the token pool registration, the pool liquidity and the root configuration. The DAO Multisig does not hold these roles. The DAO Multisig is the Kernel executor, which activates and deactivates policies. - Emergency controls. The DAO Multisig and the Emergency Multisig can each stop a route, or all routes, immediately. These controls only decrease capacity.
No design removes all risk. The bridge depends on Chainlink CCIP. A failure of CCIP or a compromise of CCIP can have an effect on the bridge. The guardrails limit that effect and give the community time to respond.
Audits
- Electisec (June 2025): the CCIP token pool and the
CCIPCrossChainBridgecontracts. - Cyfrin (October 2026): the CCIP token pool configuration policy, the configuration timelock and the rollout to the EVM chains. Cyfrin found no critical and no high issues. Of the 32 findings, 31 are resolved, and one informational finding is acknowledged.
The Electisec report and the Cyfrin report are in the Audits section.
Robinhood Chain uses the same contracts as the other EVM chains.
Contracts
The bridge contract addresses for each chain are in the contract addresses table. The holders of each role and the action matrix are in Technical Details. The roles of each contract are in Security Roles.