Full version of legacy Frax Protocol docs are currently available on docs.frax.finance (opens in a new tab)

Crosschain Strategy for Frax Assets

Overview

The Omnichain Fungible Token (OFT) (opens in a new tab) Standard allows fungible tokens to be transferred across multiple blockchains without asset wrapping, middlechains, or liquidity pools.

Frax assets are represented as OFTs on chains other than Fraxtal, and Ethereum. An OFT operates the exact same as an ERC20 with the additional function of bridge-ability through the LayerZero protocol.

All OFTs and lockboxes are audited (opens in a new tab) and managed by a 3/6 multisig on each respective chain.

Available Frax OFTs

• frxUSD
• sfrxUSD
• frxETH
• sfrxETH
• WFRAX (prev. FXS)
• FPI

Contract design

Overall, there are three types of LayerZero contracts that provide liquidity for users upon bridging:

1. OFT

• Operates as an ERC20
• When tokens are received on the chain, the OFT is minted
• When tokens are sent from the chain, the OFT is burned

2. Adapter (aka lockbox)

• Holds a running balance of a Frax-protocol token
• When tokens are received on the chain, the Adapter sends the Frax token from its' balance to the recipient
• When tokens are sent from the chain, the sender sends the Frax token to the Adapter

3. Mintable Adapter (aka mint/burn lockbox)

• Holds no balance of Frax-protocol token
• When tokens are received on the chain, the Mintable Adapter mints the Frax token to the recipient
• When tokens are sent from the chain, the Mintable Adapter burns the Frax token

With the exception of Ethereum and Fraxtal, Frax tokens are represented as an OFT. For Ethereum and Fraxtal, Frax tokens are utilized in the following:

frxUSD

• Fraxtal: Mintable Adapter
• Ethereum: Mintable Adapter

sfrxUSD

• Fraxtal: Mintable Adapter
• Ethereum: Mintable Adapter

frxETH

• Fraxtal: Mintable Adapter
• Ethereum: Adapter

sfrxETH

• Fraxtal: Mintable Adapter
• Ethereum: Adapter

WFRAX

• Fraxtal: Adapter
• Ethereum: OFT

FPI

• Fraxtal: Mintable Adapter
• Ethereum: Mintable Adapter

Hub Design

Frax OFTs are wired together as a Hub: with a single, central connection to Fraxtal, bridging from chain A to chain B can be seen as A => Fraxtal => B. The Frax team has designed a novel solution called a "Hop" which reduces the complexity in connections from N^2 to N through only connecting chains to Fraxtal. Chains connected to Fraxtal send their bridge transactions through the "Hop" contracts (opens in a new tab) which automatically forward the transaction to the destination chain. Therefore, behind the scenes, bridging from A => B is actually two transactions: A => Fraxtal and Fraxtal => B, where the second transaction is automatically handled by the LayerZero Executor via lzCompose() (opens in a new tab).

The exception to Hops are Non-EVM chains, currently Solana, Aptos, and Movement. These chains do not support the Hop contracts and instead support direction bridging to both Fraxtal and Ethereum. Therefore, bridging from Solana => B requires two seperate submitted transactions by the user: Solana => Fraxtal and Fraxtal => B. In this case, the user must wait for their bridge to Fraxtal to settle before submitting the second transaction to bridge to B.

WFRAX vs. FRAX

FRAX is the native gas token on Fraxtal. WFRAX is the wrapped version of FRAX that is used on LayerZero-powered chains, represented as an OFT.

WFRAX vs. FXS on Ethereum

There are two versions of FRAX on Ethereum: WFRAX and FXS. WFRAX is the LayerZero-powered OFT version of FRAX. FXS is the legacy version of FRAX that is not connected to the LayerZero Protocol. FXS is the original version of FRAX that was launched on Ethereum in 2020.

Users only have one option to convert their FXS into FRAX: through the native Optimism bridge.

In order to convert WFRAX to FXS, users must first either:

• If on Fraxtal: unwrap their WFRAX to FRAX.
• If on a LZ-powered chain: bridge WFRAX to Fraxtal to receive FRAX.

From there, users can convert FRAX to FXS on Ethereum through the native Optimism bridge.

Ethereum WFRAX OFT is also connected via the hub model. This means that bridging WFRAX from chain X to Ethereum will be X => Fraxtal => Ethereum. Bridging FXS to chain X will first require the user to bridge FXS to Fraxtal through the native Optimism bridge, converting their FXS to FRAX.

Current Chains

• Abstract
• Aptos
• Aurora
• Arbitrum
• Avalanche
• Base
• Berachain
• BSC
• Ethereum
• Hyperliquid
• Ink
• Linea
• Katana
• Mode
• Movement
• Optimism
• Plasma
• Plume
• Polygon
• Polygon zkEVM
• Scroll
• Sei
• Sonic
• Unichain
• Worldchain
• X-Layer
• zkSync

Process

• Bridge through the FUI (link (opens in a new tab))
• Bridge through the Stargate UI (link (opens in a new tab))
• Bridge programatically (see #Code section)

Security Considerations

Layer Zero OFT Frax Assets are not a liability of the Frax Protocol. They do not appear on the balance sheet on Frax Facts (opens in a new tab). They are not redeemable for protocol owned assets. They are only redeemable for the Frax Asset in the Layer Zero "lockbox" contract that is part of the Layer Zero Protocol.

Layer Zero OFT Frax Assets are settled by Layer Zero Decentralized Verification Networks (DVNs) that are not operated by the Frax Protocol, Frax Core Developers, or any associated entity of Frax. Therefore, the risk of OFT Frax Assets are borne by their holders. This is similar to holding "USDC tokens" on a network that its issuer, Circle, does not support minting/redeeming on. Such "USDC tokens" do not appear on Circle's balance sheet as a liability nor are they redeemable from its issuer. They are only redeemable for the underlying USDC token in the bridge (ie 'lockbox') contract.

In the future, the Frax Protocol can work with Layer Zero to upgrade certain OFT Frax Assets on select networks to allow the Frax Protocol to have direct oversight in the settlement process similar to the Frax Ferry system. After this, the OFT Frax Assets for those select networks will be reported on the associated balance sheet of those Frax Assets. When this occurs, the Frax Protocol will consider such tokens at that time as its liability that are backed directly by the assets it holds on its respective balance sheets. At this time, no Frax OFT tokens are native liabilities of the protocol.