OlympusDAO moves OHM bridging to Chainlink CCIP across seven chains

OlympusDAO has replaced the plumbing that moves its OHM token between blockchains. Transfers across seven chains now run on Chainlink’s Cross-Chain Interoperability Protocol (CCIP) instead of LayerZero.

The move was announced on November 5, 2026. The migration covers Ethereum, Arbitrum, Base, Berachain, Optimism, Solana, and Robinhood Chain. CCIP is now the canonical bridge for OHM across all seven, so there is one official route for moving the token rather than several competing ones.

The switch did not come from a single team decision. It was driven by an on-chain governance proposal, OIP-198, which passed with community support around November 2, 2026, a few days before the announcement.

What changed under the hood

On Ethereum, a lock/release pool holds canonical OHM. When tokens leave Ethereum, they get locked in that pool. When they come back, they get released.

On each destination EVM chain, Olympus controls a burn/mint pool. Tokens arriving on those chains are minted. Tokens leaving get burned. The upshot is that OHM’s total supply should stay anchored to what sits in the Ethereum vault, rather than multiplying every time someone hops networks.

Olympus also set independent rate limits for each route and each direction. Several EVM routes, for example, carry a stated capacity of 100,000 OHM.

Because the limits are set per direction, moving OHM from Ethereum to Base and moving it from Base back to Ethereum are treated as separate lanes. That gives the DAO finer control over where value flows.

Why Olympus left LayerZero

LayerZero V1 became unavailable on several chains, and bridging through V1 was disabled on layer-2 networks. That left OHM holders on those chains without the cross-chain route they had been relying on.

There was interest in restoring the old functionality by upgrading to LayerZero V2, which would have kept the DAO with its existing provider on newer infrastructure. The decision to build out CCIP was shaped by a deepening relationship with Chainlink, which already supplies price feeds to Olympus.

What users actually need to do

Nothing. Existing OHM token addresses remain the same on all supported networks. Holders do not need to swap, claim, or migrate anything. Bridging is still available through the same Olympus app interface they used before.

Integrations should also feel little friction. Exchanges, lending markets, and wallets that already list OHM on these chains reference the same contract addresses they did yesterday.

What this means

For OHM holders, the clearest near-term effect is restored and simplified access. Users on L2s who lost a working bridge when LayerZero V1 went dark now have an official route again, and it is the same route across every supported chain.

The rate limits deserve attention from anyone moving size. A 100,000 OHM cap on several EVM routes is a safety feature, but it is also a real constraint. Large holders or treasuries shifting big positions between chains may need to split transfers or wait for capacity to refresh, depending on how the limits are configured.

Consolidating onto one provider reduces complexity, but it also concentrates dependency. OHM’s cross-chain movement now runs through Chainlink’s infrastructure, and the token’s price data already relies on Chainlink feeds.

OIP-198 shows the DAO is willing to make significant infrastructure decisions through on-chain votes. Future changes, including adjustments to rate limits or the addition of new chains, would likely follow a similar path, giving token holders visibility into how the bridge evolves.