Contracts & Addresses

Upgradeable OFTs

EVM

Semi-Deterministic Addresses

Each of the 5 OFTs maintain the same address across these chains:

• Arbitrum
• Avalanche
• BSC
• Hyperliquid
• Ink
• Katana
• Optimism
• Plume
• Polygon
• Sei
• Sonic
• Stable
• Unichain
• Worldchain
• X-Layer

Random Addresses

Each address of these OFTs is unique:

• Linea, Base, Monad
  • All 5 OFTs
• Ethereum
  • WFRAX OFT

zkSync

• zkSync Era, Abstract maintain the same addresses across all 5 OFTs. This is due to the ZK compiler.

• Ethereum WFRAX
  • 0x04ACaF8D2865c0714F79da09645C13FD2888977f

Fully Deterministic Addresses (Robinhood, Somnia, Tempo)

Chains onboarded from 2026 onward share one set of 0x000000... OFT addresses, deployed with deterministic (CREATE2) deployment. On Tempo, the frxUSD address is a FraxOFTMintableAdapterUpgradeableTIP20 that mints and burns the native TIP-20 frxUSD (0x20C0000000000000000000003554d28269E0f3c2), see Tempo.

Ethereum Admin

The Timelock enforces a 24-hour delay on upgrades. The Timelock admin is a 4-of-7 Safe, which also owns the Ethereum frxUSD lockbox.

Non-EVM

All Solana OFTs use the OFT program E1ht9dUh1ZkgWWRRPCuN3kExEoF2FXiyADXeN3XyMHaQ (opens in a new tab). The OFT store is the account that EVM chains register as the Solana peer.

Lockboxes

* Ethereum WFRAX is not a lockbox but an OFT. See the "EVM" section above for details.

Retired: FPI

FPI has been retired from the mesh. The Fraxtal FPI lockbox has no peers, so FPI can no longer be bridged. For reference, the FPI contracts are:

Multisigs

Each multisig below is the LayerZero delegate of the chain's OFTs and lockboxes, and their owner, except for the Ethereum frxUSD lockbox (owned by the Timelock admin, see Ethereum Admin). It also owns the chain's ProxyAdmin, except on Ethereum (Timelock) and Fraxtal (separate 3-of-5 Safe 0xC4EB45d80DC1F079045E75D5d55de8eD1c1090E6 (opens in a new tab)).

HopV2 Contracts

All cross-chain routes relay through the Fraxtal hub. Fraxtal runs FraxtalHopV2, and each other chain runs a RemoteHopV2 and a RemoteAdmin contract (for Fraxtal-initiated admin operations). Every Hop runs version 2.0.1, and Tempo runs the RemoteHopV201Tempo variant (see Tempo). Before routing to a chain, check that it is registered on the Fraxtal Hop with remoteHop(dstEid).

Legacy Hops

The first-generation hop contracts are paused and should not be used:

• RemoteHop and FraxtalHop from fraxtal-lz-hop (opens in a new tab), including the Fraxtal hub 0x2A2019b30C157dB6c1C01306b8025167dBe1803B (opens in a new tab)
• The first HopV2 deployment, including the Fraxtal hub 0xe8Cd13de17CeC6FCd9dD5E0a1465Da240f951536 (opens in a new tab)

The MintRedeemHop contracts from fraxtal-lz-hop remain live for cross-chain frxUSD and sfrxUSD conversions. Their addresses are listed under Stake & Unstake Supported Networks.