Arbitrum Bridge vs CORE Bridge: chains, safety and fees (2026)

Both are described as canonical bridges, but they serve different routes. Arbitrum Bridge is the native channel between Ethereum and the Arbitrum rollup, with transfers in both directions and support for ETH and ERC-20 tokens. CORE Bridge is the official route into Core Network and connects it to Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, and Avalanche.

The difference in scale is substantial: Arbitrum Bridge has about $3.47 billion in TVL, compared with about $952,519 for CORE Bridge. TVL indicates the value held in a bridge, not a guarantee of safety. Still, Arbitrum’s larger figure and narrower route make it the more established option for Ethereum–Arbitrum transfers. CORE’s wider chain coverage matters if Core is your destination.

Neither bridge publishes its fees, so you cannot compare a fixed price from published fee schedules. Arbitrum Bridge notes that transfers normally involve Ethereum gas on the originating or settlement side and a small fee on Arbitrum; check the wallet or bridge quote before signing. CORE Bridge says users should expect source-chain gas and may also pay a cross-chain messaging fee. Its minimums and transfer times are not published.

Transfer timing is another distinction. Withdrawals from Arbitrum to Ethereum follow the rollup challenge period and are not instant. CORE Bridge does not publish transfer-time estimates, so do not assume that its wider chain coverage means faster settlement. Check the destination amount and estimated costs for the exact route before confirming either bridge transfer.

Arbitrum Bridge has two audits listed, but the auditors and their findings are not published. CORE Bridge has no listed audits and no published audit report. That is a meaningful difference in public audit information, though the absence of a listed audit does not prove a bridge has a vulnerability. Neither audit count should be treated as a guarantee against loss.

Both bridges involve contract risk. Arbitrum’s contracts hold user assets, while CORE Bridge also relies on LayerZero messaging; failure of the bridge contracts or messaging layer could affect bridged assets on Core. Some Core assets are wrapped versions rather than native tokens, so their backing depends on the bridge system. Use official project access points, check the route and token details, and review wallet approvals before signing. Only bridge funds you can afford to lose.

Choose by destination and asset, not just by chain count. Arbitrum Bridge is focused on moving ETH and ERC-20 tokens between Ethereum and Arbitrum. Its portal also points to Arbitrum apps and ecosystem resources. Its listed token symbol is ARB, but that does not mean the bridge only transfers ARB; the stated transfer support is ETH and ERC-20 tokens.

CORE Bridge is an entry point to Core’s Bitcoin staking and yield ecosystem. Core has specified WETH and USDC transfers from Base, and bridged assets such as USDT may appear as Core-specific wrapped tokens. Those are not native versions of the assets, and the review notes thin trading volume for wrapped USDT. Confirm the exact token and destination chain before transferring, especially when using Core-specific bridged assets.

For a transfer between Ethereum and Arbitrum, Arbitrum Bridge is the clearer pick: it is the native route, supports two-way transfers, has much higher TVL, and has two audits listed. Its limitations are its narrow chain coverage, unpublished fees, and non-instant withdrawals to Ethereum. The audit details are also not published, so the audit count should not be mistaken for a full security assessment.

Choose CORE Bridge when Core is the destination and you need a route from one of its connected chains. Its broader network coverage and LayerZero-powered transfers serve that use case, but its TVL is under $1 million and it has no listed audits. Fees, minimums, and transfer times are not published. We would favor Arbitrum Bridge for its specific route; CORE Bridge is for users who specifically need Core access and accept the additional documentation and dependency concerns.