Protocol has bridge surface
Frax Finance's assessment for RD-F-147 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Frax Finance has three distinct bridge surfaces: (1) LayerZero OFT adapter for frxUSD (0x566a6442A5A6e9895B9dCA97cC7879D632c6e4B0 — TransparentUpgradeableProxy, confirmed by Etherscan showing LayerZero Endpoint V2 interactions); (2) FraxFerry permissioned bridge for FRAX/frxETH; (3) Fraxtal OP Stack native bridge (L1 Standard Bridge Proxy 0x34c0bd5877a5ee7099d0f5688d65f4bb9158bde2). Bridge surface = TRUE, Cat 10 fully populated per profile §7.
Sources #
- EtherscanEtherscan: frxUSD OFT Adapter ProxyfrxUSD LayerZero OFT Adapter proxy 0x566a6442A5A6e9895B9dCA97cC7879D632c6e4B0 — confirmed as TransparentUpgradeableProxy with LayerZero Endpoint V2 interactionsretrieved 2026-05-17
- Frax FraxFerry Bridge DocsFrax cross-chain bridge docs — FraxFerry and Fraxtal bridge documentationretrieved 2026-05-17
- L2BEAT FraxtalL2BEAT Fraxtal — Fraxtal L1 Standard Bridge Proxy 0x34c0bd5877a5ee7099d0f5688d65f4bb9158bde2retrieved 2026-05-17
Methodology #
Determine whether the protocol has a bridge surface (its own bridge or a bridge-operated dependency for routing/minting).
See the full factor methodology and distribution across all protocols →