• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
FraxFraxby0xc3d6f21c79C2567A1858d8b93a4EDBD9dB399d9dnader

[FIP - 298] Deploy Fraxferry for sFRAX ( BSC )

Voting ended over 2 years agoSucceeded

Authors

Frax Core Team

Summary

Deploy a Fraxferry for sFRAX between Ethereum Mainnet and BSC, with the following details:

Parameter Value
Ethereum Token address 0xA663B02CF0a4b149d2aD41910CB81e23e1c41c32 (sFRAX)
BSC Token address TBD
MIN_WAIT_PERIOD_ADD 1 hour
MIN_WAIT_PERIOD_EXECUTE 23 hours

Background and Motivation

Fraxferry aims to simplify the cross-chain bridging issue for assets, making it easier to deploy Frax-related tokens on other chains. Fraxferry is a slower, simpler, but more secure method of bridging tokens. And you can read more about it here .

Proposal

  • For: Deploy a Fraxferry for sFRAX between Ethereum Mainnet and BSC
  • Against: Do nothing.

Off-Chain Vote

For
30.43M FXS100%
Against
0 FXS0%
Quorum:424%
Download mobile app to vote

Discussion

Frax[FIP - 298] Deploy Fraxferry for sFRAX ( BSC )

Timeline

Nov 13, 2023Proposal created
Nov 13, 2023Proposal vote started
Nov 18, 2023Proposal vote ended
Mar 02, 2026Proposal updated