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

[Frax] [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
238.09 pitchFXS100%
Against
0 pitchFXS0%
Download mobile app to vote

Discussion

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

Timeline

Mar 28, 2023Proposal created
Mar 28, 2023Proposal vote started
Mar 31, 2023Proposal vote ended
Jan 05, 2024Proposal updated