OHM sent out from Ethereum is locked in a pool on Ethereum and released when it returns, so bridging does not change the total supply. Olympus's documentation describes the same setup for its existing Solana route: canonical OHM is locked in an Ethereum CCIP lock-and-release token pool, and native OHM is minted on Solana. The bridge contracts for that route were audited by Electisec, the documentation says.
The earlier LayerZero setup worked differently. Under that design, OHM was burned on the source chain and minted natively on the destination rather than wrapped.
Why Olympus Switched
Crypto Briefing reports that LayerZero V1 became unavailable on several chains, and bridging through V1 was disabled on layer-2 networks. The outlet says the move leaves users on those networks with an official route again, and the same route across every supported chain.
Olympus first adopted CCIP for its Solana integration after an earlier DAO vote. In an Olympus post on Medium, the project said Chainlink's Cross-Chain Token (CCT) standard offers self-serve deployments, developer control and zero-slippage transfers.
Chainlink's documentation says that under the CCT standard, token developers retain ownership and control of token contracts, token pools and cross-chain configuration by default.
With one canonical route across all seven chains, OHM liquidity and activity can be tracked through a single bridge system rather than split between providers.
Sources
TechFlow: OlympusDAO completes migration of OHM cross-chain bridge to Chainlink CCIP
Crypto Briefing: OlympusDAO moves OHM bridging to Chainlink CCIP across seven chains
Olympus Docs: Cross-Chain OHM
bsc.news
