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

[FIP - 202] Deploy Fraxferry for FXS ( zkSync )

Voting ended almost 3 years agoSucceeded

Authors

Frax Core Team

Summary

Deploy Fraxferry for FXS between Ethereum Mainnet and zkSync Chain, with the following details:

Parameter Value
Ethereum Token address 0x3432B6A60D23Ca0dFCa7761B7ab56459D9C964D0 (FXS)
zkSync 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 Fraxferry for FXS between Ethereum Mainnet and zkSync
  • Against: Do nothing.

Off-Chain Vote

For
32.75M FXS100%
Against
0 FXS0%
Quorum:456%
Download mobile app to vote

Discussion

Frax[FIP - 202] Deploy Fraxferry for FXS ( zkSync )

Timeline

Mar 27, 2023Proposal created
Mar 27, 2023Proposal vote started
Apr 01, 2023Proposal vote ended
Mar 02, 2026Proposal updated