Fraxtal

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

REJECTED. The worklist entry measures assets locked for an OP Stack rollup, not a yield product. Fraxtal currently depends on a permissioned sequencer, upgradeable Ethereum bridge proxies, a Frax-team data-availability module, and a seven-day ordinary L2 withdrawal; official materials describe future validator security rather than a live permissionless replacement. Until a separate chain grade proves an enforceable exit window and bounds emergency authority, the bridge balance is rejected as a client position.

Kill criteria: the events that revoke this verdict
• Fraxtal receives a sourced Ketju chain grade with no active rejection criterion
• Permissionless fault proofs and forced inclusion are live and a proposed-size Ethereum exit completes without sequencer cooperation
• Every regular upgrade has an enforceable on-chain delay of at least 7 days and emergency authority is independently bounded
• The production data-availability mechanism and recovery path become independently verifiable

The research file

Mechanism and client claim

Fraxtal is an EVM-equivalent OP Stack rollup. Users bridge assets into Ethereum-side proxy contracts, transact against L2 state ordered by the sequencer, and withdraw through the standard OP Stack message path. Official bridge documentation gives Fraxtal-to-Ethereum withdrawals a seven-day duration, while Frax Mesh offers faster transfers for Frax assets through LayerZero-based OFTs and lockboxes. Those routes have different trust assumptions and cannot be blended into one claim. DefiLlama’s approximately $166M chain entry principally reflects locked backing and application assets, not an interest-bearing security.

Control, governance, and legal perimeter

Frax publishes L1 and L2 system addresses including ProxyAdmin, OptimismPortal, StandardBridge, messenger, output-oracle, and configuration proxies. The official architecture says the Frax Core Team developed the separate data-availability module, while current FRAX documentation discusses validators as a future hardfork role. Frax DAO and multisigs also control ecosystem and cross-chain contracts. Public addresses improve reproducibility but do not establish permissionless sequencing, fault proof participation, immutable data availability, or a user delay before every privileged system change.

Incident and operating record

Fraxtal has operated since 2024 and publishes network, bridge, contract and cross-chain documentation. No unreconciled system-wide bridge loss was identified in the reviewed official sources. The decision does not convert missing incident evidence into safety evidence: the chain is changing, with a roadmap toward a different security model and a Frax Mesh surface layered beside the OP bridge. A rollup can maintain perfect uptime while privileged control and data-availability assumptions still fail the registry’s chain-grade requirements.

Exit, liquidity, and failure path

The trust-minimized OP path requires the L2 withdrawal and seven-day wait before Ethereum claim; fast Frax Mesh depends on LayerZero messaging, OFT configuration, lockboxes, remote-hop contracts and multisigs. If the sequencer or data-availability path is impaired, an independent exit depends on the deployed proof and portal machinery. The worklist value cannot establish same-day liquidity or protect a client from bridge discount. Asset-specific issuer redemption may exist for frxUSD, but that is a separate issuer claim and does not make the chain bridge sovereign.

Comparison and decision

Ethereum-native ownership avoids sequencer, data-availability, portal-proxy, OFT and lockbox risks. Arbitrum and Base at least have complete chain grades and live fault-proof evidence, though both remain limited; Fraxtal should not inherit their verdict merely because it uses OP Stack code. Reopen after a dedicated chain review maps sequencing, proof participation, data publication, admin thresholds, emergency powers and both exit routes. Until then, the correct disposition is infrastructure tracked at zero, not a $166M protocol endorsement.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Fraxtal Docs — About Fraxtal · primary · accessed 2026-08-19
  Supports: OP Stack, team data availability, rollup design
• Fraxtal Docs — bridges · primary · accessed 2026-08-19
  Supports: OP bridge, seven-day withdrawal, Frax Mesh
• Fraxtal Docs — system contracts · primary · accessed 2026-08-19
  Supports: ProxyAdmin, portal, bridge, messenger
• Frax Docs — FRAX token · primary · accessed 2026-08-19
  Supports: native gas token, future validator role, token economics
• Frax Docs — cross-chain addresses · primary · accessed 2026-08-19
  Supports: upgradeable OFTs, lockboxes, multisigs
• DefiLlama — Fraxtal protocol data · secondary · accessed 2026-08-19
  Supports: protocol category, chain perimeter, current TVL

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.