Crosschain Configuration

Every Frax OFT and lockbox is a LayerZero V2 OApp (opens in a new tab). Frax sets the message libraries, DVNs, block confirmations, and enforced options of every pathway explicitly. Only the executor is left at LayerZero's default. All five Frax OFTs (frxUSD, sfrxUSD, frxETH, sfrxETH, WFRAX) use the same settings on a given pathway.

The values on this page were read on-chain on October 6, 2026. They match the configuration files in frax-oft-upgradeable (opens in a new tab): config/dvn (opens in a new tab), config/confirmations (opens in a new tab), and scripts/L0Config.json (opens in a new tab).

Pathways

Every chain is wired to Fraxtal (EID 30255) and to no other chain. A transfer between two other chains is two LayerZero messages, A → Fraxtal → B, which HopV2 chains together from a single user transaction. Only the pathways listed on this page are supported.

Summary

Message Libraries

Each OFT sets its send and receive library for every peer with EndpointV2.setSendLibrary and EndpointV2.setReceiveLibrary (no grace period). When LayerZero publishes a new default library, Frax pathways keep their current library until the delegate migrates them.

DVNs

Frax uses a required-only DVN stack. A message is committed on the destination chain only after every DVN on its pathway has verified it.

• Every DVN is required. requiredDVNCount equals the size of the stack, and there are no optional DVNs: optionalDVNCount is set to the NIL value and optionalDVNThreshold to 0. A single DVN withholding its verification stops delivery, and no subset of the stack can deliver a message.
• Same operators in both directions. An operator is part of a pathway only if it runs a DVN on both chains. Both directions of a pathway use the same operators, while each operator's DVN contract address differs per chain.
• Somnia pathways use four DVNs because Canary does not operate a DVN on Somnia.

Frax DVN

Frax operates one of the required DVNs on every chain in the mesh. Each deployment is LayerZero's standard DVN contract (FraxDVN.sol (opens in a new tab)), and every verification needs signatures from 2 of its 3 signers. Because the Frax DVN is required on every pathway, every Frax OFT message is verified by Frax in addition to the other DVNs.

DVN addresses

The table lists the DVN contracts used on each chain's pathway with Fraxtal. On Fraxtal, the same five contracts serve every pathway.

Block Confirmations

DVNs wait for a number of block confirmations on the source chain before they verify a message. Messages sent from Fraxtal wait for 5 Fraxtal blocks. Messages sent to Fraxtal wait for the count listed for their source chain in Settings by Chain.

Confirmation counts are fixed in each OFT's configuration, so a change to LayerZero's recommended values does not apply until Frax updates the pathway. Most counts equal LayerZero's recommended value for the chain, including X-Layer's 225,000 blocks. Frax waits longer than the recommended 20 blocks on Ink (60), Katana (60), Optimism (24), Unichain (72), and Worldchain (60).

Enforced Options

Enforced options set the minimum executor options that every send must carry, so a sender can pass empty extraOptions and the message still has enough gas to execute on the destination. Options passed in extraOptions are added on top of the enforced options: they can add gas or native value, but they cannot go below the minimum.

Frax sets enforced options for both OFT message types:

• SEND (msgType 1): a plain transfer
• SEND_AND_CALL (msgType 2): a transfer with a composeMsg

All values are lzReceive executor options. Enforced options cover only lzReceive. A send that carries a composeMsg must add its own lzCompose option in extraOptions; HopV2 adds it automatically. The SOL amount sent to Solana (2,500,000 lamports) pays the rent for the recipient's token account when it does not exist yet.

Settings by Chain

Executor

Frax does not set an executor configuration, so every pathway uses LayerZero's default executor and default maximum message size (10,000 bytes on EVM pathways). If LayerZero changes its default executor, Frax pathways follow automatically.

Delegate and Admin

The OFT owner and the LayerZero delegate is the Frax admin multisig on each chain, listed under Multisigs. The delegate is the only address that can change a pathway's libraries, DVNs, confirmations, or enforced options.

• On every EVM chain other than Ethereum, the admin multisig is a 3-of-6 Safe. On Solana, it is a Squads multisig.
• On Ethereum, the admin multisig is a 3-of-5 Safe. The frxUSD lockbox is owned by a separate 4-of-7 Safe, which also administers the Timelock that owns the Ethereum ProxyAdmin. Ethereum upgrades therefore wait 24 hours.
• On Fraxtal, the ProxyAdmin is owned by a separate 3-of-5 Safe.

HopV2

HopV2 (opens in a new tab) routes transfers between two non-Fraxtal chains through Fraxtal. It does not change the OFT pathway configuration above: each leg is an ordinary OFT send that uses the pathway's DVNs, confirmations, and enforced options. HopV2 adds the following settings of its own:

numDVNs and executorOptions only affect fee quotes. The Fraxtal → destination leg is executed with the destination's enforced options, plus the lzCompose gas when data is set.

Verifying On-Chain

The examples use Foundry's cast (opens in a new tab) and the frxUSD OFT on Arbitrum. Substitute the endpoint, library, OFT, and EID for any other pathway.

Read the DVN configuration (config type 2) that Arbitrum uses to send to Fraxtal:

cast call 0x1a44076050125825900e736c501f859c50fE728c \
  "getConfig(address,address,uint32,uint32)(bytes)" \
  0x80Eede496655FB9047dd39d9f418d5483ED600df \
  0x975bcD720be66659e3EB3C0e4F1866a3020E493A 30255 2 \
  --rpc-url https://arb1.arbitrum.io/rpc
 
# Decode the result as (confirmations, requiredDVNCount, optionalDVNCount,
# optionalDVNThreshold, requiredDVNs, optionalDVNs)
cast abi-decode "f()((uint64,uint8,uint8,uint8,address[],address[]))" <result>
# (20, 5, 0, 0, [0x19670Df5..., 0x2f55C492..., 0xa7b5189b..., 0xB42726e4..., 0xf2E380c9...], [])

Use the ReceiveUln302 address to read the receive side. Read the enforced options for SEND (1) and SEND_AND_CALL (2):

cast call 0x80Eede496655FB9047dd39d9f418d5483ED600df \
  "enforcedOptions(uint32,uint16)(bytes)" 30255 1 \
  --rpc-url https://arb1.arbitrum.io/rpc
# 0x00030100110100000000000000000000000000030d40  -> lzReceive gas 200,000 (0x030d40)

Confirm that the library is set explicitly rather than inherited from the default:

cast call 0x1a44076050125825900e736c501f859c50fE728c \
  "isDefaultSendLibrary(address,uint32)(bool)" \
  0x80Eede496655FB9047dd39d9f418d5483ED600df 30255 \
  --rpc-url https://arb1.arbitrum.io/rpc
# false