bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 15쪽 중 2쪽
M
chainId
.
Checklist before using the bridge
Section titled “Checklist before using the bridge”
Peers wired correctly:
EVM
peers(30168)
==
0x067c7c6c...2e661649
(Solana program).
Solana PeerConfig for
30101
==
0x000..001e1d4278...01b8
(Ethereum adapter).
Adapter token = USDS (
0xdc035d...7384f
) on Ethereum.
Quote → Send works both directions with sufficient options (lzReceive gas / lamports for ATA).
Small test transfers succeed without manual redemption.
Transfer semantics
Section titled “Transfer semantics”
Because the Ethereum side uses an OFT Adapter for an existing token (USDS), while the Solana side runs an OFT program, the debit/credit behavior is:
Ethereum → Solana: the adapter locks USDS on Ethereum and the Solana OFT mints USDS to the recipient on Solana.
Solana → Ethereum: the Solana OFT burns USDS on Solana and the Ethereum adapter unlocks USDS to the recipient on Ethereum.
No claim step: once the message is delivered and executed with sufficient options/fees, crediting happens automatically on the destination (Executor executes the destination
lzReceive
).
How to bridge USDS
Section titled “How to bridge USDS”
Solana ➜ Ethereum
Section titled “Solana ➜ Ethereum”
Inputs you must provide
Destination EID:
30101
(Ethereum).
Recipient: 20-byte EVM address encoded as
bytes32
(left-pad zeros to 32 bytes).
Amount: USDS amount (local decimals on Solana OFT).
Options (destination execution on EVM): include enough lzReceive gas so the EVM credit step can run. (If your pathway enforces defaults, they are merged with your per-tx options.)
Quote fees on Solana
Use the Solana OFT SDK’s quote function for this program to get the
nativeFee
(denominated in lamports) for
dstEid=30101
,
to(bytes32)
,
amountLD
,
minAmountLD
,
options
. (The SDK uses the Endpoint to aggregate DVN + Executor fees into
nativeFee
.)
Send on Solana
Call the Solana OFT SDK
send
instruction, paying the returned
nativeFee
(plus normal Solana tx fees — base 5,000 lamports/signature; add priority fee if desired). After delivery + execution, the Ethereum adapter unlocks USDS to the recipient.
If per-tx options are missing or too low, you may hit errors (e.g., insufficient lzReceive gas). Ensure options cover the EVM mint/unlock call. Options are merged with any enforced options on the pathway.
Ethereum ➜ Solana
Section titled “Ethereum ➜ Solana”
Inputs you must provide
Destination EID:
30168
(Solana).
Recipient: 32-byte Solana address supplied to the adapter as
bytes32
(ed25519 pubkey bytes).
Amount: USDS amount (ERC-20 decimals).
Options: if the recipient’s Associated Token Account (ATA) for USDS may not exist on Solana, include lamports for rent in options so the Executor can create it during
lzReceive
. A standard SPL token account requires
2,039,280
lamports for rent-exemption. Provide this per transfer rather than enforcing globally.
Approve USDS to the adapter
On Ethereum, call ERC-20
approve(spender, amount)
where
spender = 0x1e1D42781FC170EF9da004Fb735f56F0276d01B8
.
The OFT Adapter will pull tokens when sending. (This is standard for OFT Adapter with existing tokens.)
Quote fees (EVM)
Call
IOFT.quoteSend(SendParam, payInLzToken)
with
payInLzToken=false
to pay in ETH. Read
MessagingFee.nativeFee
. (If you choose to pay with ZRO, use
lzTokenFee
.)
Send (EVM)
Call
IOFT.send(SendParam, MessagingFee, refundAddress)
and pass
nativeFee
in
msg.value
. After delivery + execution, the Solana OFT mints USDS to the recipient’s ATA. If you included ATA rent in options and the ATA didn’t exist, the program can create it during execution.
Fees & options
Section titled “Fees & options”
Quoting is required before sending
EVM:
quoteSend
returns
MessagingFee
with
nativeFee
and optional
lzTokenFee
(ZRO). Most users set
payInLzToken=false
and pay
nativeFee
in ETH.
Solana: the OFT SDK returns a
nativeFee
in lamports which you include in your
send
instruction (you also pay normal Solana tx fees).
Options model (destination gas/value)
Your per-tx options are combined with enforced options on the pathway using LayerZero’s Option Builder semantics; don’t duplicate the same option or you’ll overpay. Use
msgType = SEND (1)
for enforced-options lookups.
Deployment-specific constants & encodings
Section titled “Deployment-specific constants & encodings”
Use these exact bytes32 values when verifying peers on-chain.
Solana OFT program as
bytes32
(for EVM peer at
eid=30168
)
SKYTAiJRkgexqQqFoqhXdCANyfziwrVrzjhBaCzdbKW
→
0x067c7c6c60ba7f1aec14059100df74d6da07e7d31da5dd756c6308f02e661649
Ethereum adapter address as
bytes32
(for Solana peer at
eid=30101
)
0x1e1D42781FC170EF9da004Fb735f56F0276d01B8
→
0x0000000000000000000000001e1d42781fc170ef9da004fb735f56f0276d01b8
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/skylink/base-eth-native-bridge
Base ETH Native Bridge
Level:
Beginner
Estimated Time:
15 minutes
Last Updated
: 2024-11-20
The SkyLink Ethereum-Base Native Bridge is designed to simplify the process of transferring tokens between the Ethereum and Base networks. This guide explains how you can deposit and withdraw supported tokens—specifically USDS and sUSDS—using this bridge. Customizations made to the bridge (from the original OP Stack bridge codebase) allow Sky Ecosystem governance to manage token support and add new features when needed. By following this guide, you will learn how to use the bridge effectively, including specific steps for token transfers and how SkyLink governance can adapt the bridge to meet future needs.
Learning objectives
Section titled “Learning objectives”
Understand the purpose and functionality of the SkyLink Ethereum-Base Native Bridge
Learn how to deposit and withdraw USDS and sUSDS between Ethereum and Base
Identify the tokens currently supported by the bridge
Gain familiarity with the governance mechanisms that control bridge operations and updates
Pre-requisites
Section titled “Pre-requisites”
Familiarity with ERC20 tokens.
Guide
Section titled “Guide”
Deployment Details
Section titled “Deployment Details”
Tokens
Section titled “Tokens”
Component
Network
Address
USDS Token
Ethereum
0xdC035D45d973E3EC169d2276DDab16f1e407384F
USDS Token
Base
0x820C137fa70C8691f0e44Dc420a5e53c168921Dc
sUSDS Token
Ethereum
0xa3931d71877C0E7a3148CB7Eb4463524FEc27fbD
sUSDS Token
Base
0x5875eEE11Cf8398102FdAd704C9E96607675467a
Core Base Components
Section titled “Core Base Components”
Component
Network
Address
MESSENGER
Ethereum
0x866E82a600A1414e583f7F13623F1aC5d58b0Afa
MESSENGER
Base
0x4200000000000000000000000000000000000007
SkyLink Bridge
Section titled “SkyLink Bridge”
Component
Network
Address
BASE_TOKEN_BRIDGE
Ethereum
0xA5874756416Fa632257eEA380CAbd2E87cED352A
BASE_TOKEN_BRIDGE Implementation
Ethereum
0xaeFd31c2e593Dc971f9Cb42cBbD5d4AD7F1970b6
BASE_TOKEN_BRIDGE
Base
0xee44cdb68D618d58F75d9fe0818B640BD7B8A7B7
BASE_TOKEN_BRIDGE Implementation
Base
0x289A37BE5D6CCeF7A8f2b90535B3BB6bD3905f72
SkyLink Escrow
Section titled “SkyLink Escrow”
Component
Network
Address
SKY_BASE_ESCROW
Ethereum
0x7F311a4D48377030bD810395f4CCfC03bdbe9Ef3
SkyLink Governance Relay
Section titled “SkyLink Governance Relay”
Component
Network
Address
BASE_GOV_RELAY
Ethereum
0x1Ee0AE8A993F2f5abDB51EAF4AC2876202b65c3b
BASE_GOV_RELAY
Base
0xdD0BCc201C9E47c6F6eE68E4dB05b652Bb6aC255
ChainLog
Section titled “ChainLog”
ChainLog
deployed at
0xdA0Ab1e0017DEbCd72Be8599041a2aa3bA7e740F
stores the following data on-chain for the SkyLink Ethereum-Base Native Bridge.
BASE_GOV_RELAY
BASE_ESCROW
BASE_TOKEN_BRIDGE
BASE_TOKEN_BRIDGE_IMP
Usage
Section titled “Usage”
Access Portals
Section titled “Access Portals”
Superbridge
Section titled “Superbridge”
Users can transfer USDS and sUSDS between Ethereum and Base on Suprbridge at
https://superbridge.app/
Bridgg
Section titled “Bridgg”
Users can transfer USDS and sUSDS between Ethereum and Base on Bridgg at
https://www.brid.gg/
Depositing Tokens from Ethereum to Base
Section titled “Depositing Tokens from Ethereum to Base”
To deposit tokens from Ethereum to Base, follow these steps:
Approve the Bridge Contract:
Allow the L1TokenBridge contract on Ethereum (BASE_TOKEN_BRIDGE) to spend the desired amount of tokens.
IERC20
(USDS)
.
approve
(l1TokenBridge, amount);
Initiate the Deposit:
Call the
bridgeERC20To
function on the
L1TokenBridge
contract to begin the deposit.
l1TokenBridge
.
bridgeERC20To
(
l1Token,
// Address of the L1 token
l2Token,
// Address of the corresponding L2 token
recipient,
// Address receiving tokens on L2
amount,
// Amount of tokens to deposit
minGasLimit,
// Minimum gas limit for the L2 execution
extraData
// Optional extra data
);
Token Locking:
The tokens are transferred to the Escrow contract on Ethereum.
Message Relay:
A cross-chain message is sent to the
L2TokenBridge
via the
L1CrossDomainMessenger
.
Token Minting:
The
L2TokenBridge
mints the equivalent amount of tokens on Base for the recipient.
Withdrawing Tokens from Base to Ethereum
Section titled “Withdrawing Tokens from Base to Ethereum”
To withdraw tokens from Base back to Ethereum, follow these steps:
Approve the
L2TokenBridge
Contract:
Allow the
L2TokenBridge
contract on Base (BASE_TOKEN_BRIDGE) to spend the desired amount of tokens.
IERC20
(l2Token)
.
approve
(l2TokenBridge, amount);
Initiate the Withdrawal:
Call the
bridgeERC20To
function on the
L2TokenBridge
contract to begin the withdrawal.
l2TokenBridge
.
bridgeERC20To
(
l2Token,
// Address of the L2 token
l1Token,
// Address of the corresponding L1 token
recipient,
// Address receiving tokens on L1
amount,
// Amount of tokens to withdraw
minGasLimit,
// Minimum gas limit for the L1 execution
extraData
// Optional extra data
);
Token Burning:
This token amount is burned on Base.
Message Relay:
A cross-chain message is sent to the
L1TokenBridge
via the
L2CrossDomainMessenger
.
Security Period:
Withdrawals are subject to a ~7-day security delay due to the OP Stack architecture. After this period, the withdrawal can be finalized.
Token Release:
The
L1TokenBridge
releases the tokens from the
Escrow
back to the recipient on Ethereum.
Check Token Support
Section titled “Check Token Support”
To verify if a token on Ethereum is supported by the bridge and has a counterpart on Base, use the
l1ToL2Token
function available on the bridge contracts deployed on both Ethereum and Base networks.
Limits
Section titled “Limits”
Currently, there are no limits on the amount of tokens that users can transfer between Ethereum and Base.
A maximum withdrawal limit (
maxWithdraw
) can be set by governance on the bridge contract deployed to Base, for each supported token individually. This limit restricts the maximum amount that can be withdrawn in a single transaction. However, users can submit multiple transactions, as the maxWithdraw limit does not decrease after each withdrawal. Currently, the maxWithdraw limit is set to
UINT_MAX
for all supported tokens, allowing users to transfer any amount from Base to Ethereum in a single transaction.
In the future, Sky Ecosystem governance may adjust the maxWithdraw limit for transfers from Base to Ethereum.
Fees
Section titled “Fees”
Users are responsible for paying gas fees for transactions on both the Ethereum and Base networks. This includes the cost of cross-chain messaging through Base’s cross-domain messengers on both networks.
Your wallet or user interface may also charge fees for using their infrastructure during deposit and withdrawal transactions.
The bridge contracts do not charge any additional fees.
Escrow
Section titled “Escrow”
When tokens are deposited from Ethereum to Base, they are transferred to the
Escrow
contract on Ethereum, where they are held securely. During withdrawals from Base back to Ethereum, once the cross-chain message is confirmed and finalized, the tokens are released from the Escrow contract to the user’s address on Ethereum.
Sky Ecosystem Governance
Section titled “Sky Ecosystem Governance”
Sky Ecosystem Governance manages all aspects of bridge governance.
Token Support
Section titled “Token Support”
Governance can add support for new tokens by using the
registerToken()
function, which allows onboarding an existing token on Ethereum along with its counterpart on Base, or vice versa. This function is executed in the bridge contracts on both networks.
Bridge Upgrades
Section titled “Bridge Upgrades”
Governance can use the UUPS upgradeability feature on the bridge contracts on Ethereum and Base to update their respective implementations and add new features as needed.
Governance can also close the existing bridge deployments with the
close()
function. After closing, a new bridge contract can be deployed to interact with the existing Escrow contract that holds token balances.
Governance Relay
Section titled “Governance Relay”
Governance can directly exert control over contracts deployed on Base by sending cross-chain messages through
L1GovernanceRelay
and
L1GovernanceRelay
. These governance relay contracts utilize the messaging infrastructure that Base provides. Governance can send a message using
L1GovernanceRelay
to
L2GovernanceRelay
which receives it and executes governance actions on Base.
Closing a Bridge
Section titled “Closing a Bridge”
Governance can call the
close()
function on either the Ethereum or Base side of the bridge independently. This changes the
isOpen
status from
1
to
0
on the bridge contract where
close()
is executed, preventing any further transactions. If the bridge contract on Ethereum is closed, users cannot initiate new deposits to Base. If the bridge contract on Base is closed, users cannot initiate withdrawals from Base to Ethereum.
Summary
Section titled “Summary”
The SkyLink Ethereum-Base Native Bridge allows users to easily transfer USDS and sUSDS tokens between Ethereum and Base networks. This guide covered the essential steps for depositing and withdrawing tokens, including contract approvals, cross-chain messaging, and understanding the governance that controls bridge operations. Governance features provide flexibility for adding new tokens, making updates, and setting limits for withdrawals, ensuring the bridge remains functional and adaptable.
Users can utilize either
Superbridge
or
Bridgg
to facilitate these transfers, both offering easy and secure interfaces. Be aware that standard gas fees apply for transactions on both networks, and cross-chain messaging fees may also apply.
Resources
Section titled “Resources”
Codebase
Technical Docs and Architecture
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/overview
Overview
Sky Ecosystem’s governance is transitioning from MKR token to the native SKY token. This upgrade marks a key milestone in Sky’s evolution from its MakerDAO roots and empowers SKY holders with full protocol control.
Document Structure
Section titled “Document Structure”
To navigate this guide:
Key Information
: contract addresses and portals.
Upgrade Timeline
: phases and dates.
Token Holders
: conversion steps before/after activation.
Protocol Participants
: voting and staking workflows.
Integrators
: info for integrators.
Codebase Change Analysis
: changes between old and new versions.
Chief Cutover Checks
: monitoring governance cutover process.
Vote Data API
: monitoring governance cutover process.
Troubleshooting
: common issues and steps to resolve.
Key Changes
Section titled “Key Changes”
Governance Token
MKR replaced by SKY for all on‑chain votes and protocol parameters on the new Chief governance contract.
Conversion Model
The current Bi‑directional conversion model between MKR and SKY becomes uni‑directional.
Delayed Upgrade Penalty
SKY holders can vote on penalty percentage for delayed upgrades after specified deadlines.
Audience & Next Steps
Section titled “Audience & Next Steps”
Token Holders
Learn how and when to convert your MKR to SKY →
Token Holders
Protocol Participants
Understand the timing to switch voting, delegation, and staking workflows →
Protocol Participants
Integrators
Prepare your UIs, back‑ends, and tooling for SKY‑driven governance →
Integrators
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/key-info
Key Information
Portals
Section titled “Portals”
MakerDAO Voting Portal
Section titled “MakerDAO Voting Portal”
vote.makerdao.com
Only available to withdraw MKR from your current delegate contract and Chief V2.
Sky Voting Portal
Section titled “Sky Voting Portal”
vote.sky.money
Live for SKY holders’ votes in Chief V3.
Sky Portal
Section titled “Sky Portal”
sky.money
Convert MKR to SKY. Upgrade Seal Engine rewards and borrowing positions and earn rewards. Functionality of the portal may vary by jurisdiction.
Contract Addresses
Section titled “Contract Addresses”
Tokens
Section titled “Tokens”
SKY Token
Section titled “SKY Token”
Address:
0x56072C95FAA701256059aa122697B133aDEd9279
Codebase:
https://github.com/sky-ecosystem/sky
MKR-SKY One Way Converter V2
Section titled “MKR-SKY One Way Converter V2”
Address:
0xA1Ea1bA18E88C381C724a75F23a130420C403f9a
Chronicle SKY USD Price Feed
Section titled “Chronicle SKY USD Price Feed”
Address:
0xc2ffbbDCCF1466Eb8968a846179191cb881eCdff
SKY USD Price Feed with Delay
Section titled “SKY USD Price Feed with Delay”
Address:
0x511485bBd96e7e3a056a8D1b84C5071071C52D6F
MKR Token
Section titled “MKR Token”
Address:
0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2
Codebase:
https://github.com/sky-ecosystem/ds-token
Staked SKY Token (lssky)
Section titled “Staked SKY Token (lssky)”
Address:
0xf9A9cfD3229E985B91F99Bc866d42938044FFa1C
Governance Contracts
Section titled “Governance Contracts”
Chief
Section titled “Chief”
Chief V3 (SKY)
Section titled “Chief V3 (SKY)”
Address:
0x929d9A1435662357F54AdcF64DcEE4d6b867a6f9
Codebase:
https://github.com/sky-ecosystem/chief
Chief V2 (MKR)
Section titled “Chief V2 (MKR)”
Address:
0x0a3f6849f78076aefadf113f5bed87720274ddc0
Codebase:
https://github.com/sky-ecosystem/ds-chief
Chief V1 (Single Collateral Dai & Multi Collateral Dai, 2017)
Section titled “Chief V1 (Single Collateral Dai & Multi Collateral Dai, 2017)”
Address:
0x8E2a84D6adE1E7ffFEe039A35EF5F19F13057152
Codebase:
https://github.com/sky-ecosystem/ds-chief/tree/a06b5e426a30e1471b93093857760b85e2fcb93a
Vote Delegate
Section titled “Vote Delegate”
Vote Delegate V3 (supports SKY + Chief V3)
Section titled “Vote Delegate V3 (supports SKY + Chief V3)”
Address:
0x4Cf3DaeFA2683Cd18df00f7AFF5169C00a9EccD5
Codebase:
https://github.com/sky-ecosystem/vote-delegate/tree/v3
Vote Delegate V2 (supports MKR + Chief V2. Used by Seal Engine V1)
Section titled “Vote Delegate V2 (supports MKR + Chief V2. Used by Seal Engine V1)”
Address:
0xc3d809e87a2c9da4f6d98fecea9135d834d6f5a0
Codebase:
https://github.com/sky-ecosystem/vote-delegate/tree/25b63b079ea6ef3ba875a983ddc4265971b867d3
Vote Delegate V1 (supports MKR + Chief V2)
Section titled “Vote Delegate V1 (supports MKR + Chief V2)”
Address:
0xd897f108670903d1d6070fcf818f9db3615af272
Codebase:
https://github.com/sky-ecosystem/vote-delegate/tree/v1
Staking Engine
Section titled “Staking Engine”
Staking Engine (supports Chief V3 SKY )
Section titled “Staking Engine (supports Chief V3 SKY )”
Address:
0xCe01C90dE7FD1bcFa39e237FE6D8D9F569e8A6a3
Codebase:
https://github.com/sky-ecosystem/lockstake/tree/v2
SKY USDS Rewards (Staking Engine)
Section titled “SKY USDS Rewards (Staking Engi프로젝트로 돌아가기