Skip to content

Latest commit

 

History

History
17 lines (9 loc) · 2.83 KB

bridged-gyd.md

File metadata and controls

17 lines (9 loc) · 2.83 KB

Bridged GYD

The main GYD contracts are deployed on Ethereum, which is where minting and redeeming of GYD takes place. GYD is accessible on L2s through a bridge. Limited amounts of GYD can be acquired directly on L2s via special AMO pools, which hold limited amounts of reserve assets on L2s.

Bridge contracts are deployed in an upgradeable way that allows bridge providers to be switched by governance in the future.

Arbitrum

The GYD bridge between Ethereum and Arbitrum currently uses Chainlink CCIP. The bridge works by a standard lock-and-mint mechanism and communicates with Arbitrum through CCIP message passing.

ContractChainPurposeAddress
GydL1CCIPEscrowEthereumEntry point for bridging. Holds GYD bridged to L20xa1886c8d748DeB3774225593a70c79454B1DA8a6
L2GydArbitrumGYD Token contract on L2. L2 entry point for bridging0xCA5d8F8a8d49439357d3CF46Ca2e720702F132b8
CCIP RouterEthereumUsed in the background for communication0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D
CCIP RouterArbitrumLikewise0x141fa059441E0ca23ce184B6A78bafD2A517DdE8

Polygon zkEVM

The GYD bridge between Ethereum and Polygon zkEVM currently uses the native Polygon zkEVM bridge.

ContractChainPurposeAddress
GydL1EscrowEthereumEntry point for bridging. Holds GYD bridged to L20xF3387a880998C9B9169bc9973E8826Fc9035c171
L2GydzkEVMGYD Token contract on L2. L2 entry point for bridging0xCA5d8F8a8d49439357d3CF46Ca2e720702F132b8
PolygonZkEVMBridgeV2EthereumUsed in the background for communication0x2a3DD3EB832aF982ec71669E178424b10Dca2EDe
PolygonZkEVMBridgeV2zkEVMLikewise0x2a3DD3EB832aF982ec71669E178424b10Dca2EDe