5 chains lost Frax OFT bridge support on 30 July 2026: Aptos, Berachain, Mode, Movement and Scroll. The change followed FIP-445, which discontinued Frax OFT routes on those networks after a governance decision. Anyone holding affected Frax assets needed to unwind positions and bridge back before the deadline; after it, transfers to and from the deprecated chains were scheduled to stop.
What happened on 30 July 2026?
The event was the full deactivation of Frax OFT bridge support for five networks. Frax announced the deadline in its 19 June 2026 ecosystem update, while the underlying FIP-445 governance proposal was posted on 21 May 2026.
The affected assets include frxUSD, sfrxUSD, frxETH, sfrxETH, FPI and WFRAX. The proposal says the affected chains had either been deprecated by their core teams or showed prolonged inactivity and low adoption.
“Discontinuing support will simplify network operations, reduce risk exposure, and ensure efficient maintenance of the active Frax Mesh.” — Frax Core Team
Frax’s proposal describes the final state clearly: sends from a deprecated chain to Fraxtal are disabled, receiving from that chain is blocked, and the peer mapping is reset. The event therefore touches the Frax OFT contracts, Fraxtal, the five named networks, LayerZero messaging configuration and applications that display or route these assets. The Frax Swap interface belongs in the route check because users should not assume that an interface still offers a deprecated path.
Which chains lost Frax OFT bridge support?
| Chain | What changed | Who needed to act | Deadline |
|---|---|---|---|
| Aptos | Frax OFT support deprecated | Liquidity providers and token holders | 30 July 2026 |
| Berachain | Frax OFT support deprecated | Liquidity providers and token holders | 30 July 2026 |
| Mode | Frax OFT support deprecated | Liquidity providers and token holders | 30 July 2026 |
| Movement | Frax OFT support deprecated | Liquidity providers and token holders | 30 July 2026 |
| Scroll | Frax OFT support deprecated | Liquidity providers and token holders | 30 July 2026 |
The deadline has passed as of 10 August 2026. Holders who did not move assets beforehand should not retry a failed route repeatedly or send tokens to an old contract without first checking the current Frax documentation and the destination chain’s status.
Why does an OFT deprecation stop transfers?
An Omnichain Fungible Token is designed to represent one fungible asset across multiple blockchains. The LayerZero OFT documentation explains that the standard debits tokens on the source chain and credits the equivalent amount on the destination chain, preserving a unified supply. If the endpoint, peer mapping or execution configuration for one chain is removed, the cross-chain message no longer has a supported destination.
This is different from a normal exchange delisting. A delisting removes a trading pair from a marketplace; an OFT deprecation removes a cross-chain transport path. The token may still exist on the affected chain, but its Frax-controlled route back to Fraxtal or another supported network may be unavailable.
What should users do now?
- Identify whether the wallet holds a Frax OFT asset on Aptos, Berachain, Mode, Movement or Scroll.
- Check whether a current, supported withdrawal or migration route is displayed by the relevant Frax interface.
- Do not treat a token balance on a deprecated chain as proof that the bridge remains usable.
- For liquidity providers, review pool positions separately: removing liquidity and moving the resulting asset are different transactions.
The decision is straightforward. Users who moved before 30 July followed the intended exit path. Users with assets still on a named chain need a verified current route or direct support guidance. Developers and aggregators must remove the five deprecated networks from route lists, token selectors and bridge configuration. The broader DeFi context is that open protocols are composable but remain dependent on the smart contracts, message endpoints and applications that connect them; Ethereum’s DeFi guide describes these layers as separate parts of the same stack.