OlympusDAO Migrates OHM Bridging to Chainlink CCIP Across Seven Chains

OlympusDAO has moved OHM bridging to Chainlink's Cross-Chain Interoperability Protocol across seven chains, replacing LayerZero following an on-chain governance vote that passed around November 2, 2026. The protocol announced the completed migration on November 5, 2026.

CCIP is now the canonical bridge for OHM on Ethereum, Arbitrum, Base, Berachain, Optimism, Solana, and Robinhood Chain. That means one official route moves the token between networks, rather than several competing paths.

The decision didn't come from a core team unilaterally. It ran through governance proposal OIP-198, which passed with community support days before the announcement. Token holders voted on-chain to swap infrastructure providers — the kind of operational call many protocols still make behind closed doors.

What changed under the hood?

The new architecture uses a lock-and-mint model anchored to Ethereum. On Ethereum itself, a lock/release pool holds canonical OHM. Tokens leaving the mainnet get locked in that pool; tokens returning get released.

Each destination EVM chain runs a burn/mint pool controlled by Olympus. Arriving tokens are minted on the destination chain, and departing tokens are burned. The design keeps OHM's total supply anchored to the balance sitting in the Ethereum vault, rather than letting supply multiply every time a user hops networks.

Olympus also set independent rate limits for each route and each direction. Several EVM routes carry a stated capacity of 100,000 OHM. Because limits apply per direction, an Ethereum-to-Base transfer and a Base-to-Ethereum transfer operate as separate lanes. That gives the DAO fine-grained control over where value can flow.

Why did Olympus leave LayerZero?

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

The DAO considered restoring old functionality by upgrading to LayerZero V2, which would have kept the existing provider on newer infrastructure. Instead, the decision to build out CCIP was shaped by a deepening relationship with Chainlink, which already supplies price feeds to Olympus. Chainlink is now the dependency for both OHM's price data and its cross-chain movement.

What do users need to do?

Nothing. Existing OHM token addresses remain unchanged on all supported networks. Holders don't need to swap, claim, or migrate tokens. Bridging still runs through the same Olympus app interface.

Integrations should see minimal friction. Exchanges, lending markets, and wallets that already list OHM on these chains reference the same contract addresses they did before the migration — no relistings or contract updates required.

What are the practical consequences?

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

The rate limits matter to anyone moving size. A 100,000 OHM cap on several EVM routes is a safety feature, but it's also a real constraint. Large holders or treasuries shifting 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 cuts complexity, but it concentrates dependency. OHM's cross-chain movement now runs entirely through Chainlink's infrastructure, on top of the token's existing reliance on Chainlink price feeds — a single point of vendor risk across two critical functions.

OIP-198 also signals how the DAO plans to handle infrastructure going forward. Future changes, including rate-limit adjustments or the addition of new chains, would likely follow the same on-chain voting path, giving token holders direct visibility — and a vote — on how the bridge evolves.