The Sonic mainnet was rolled out earlier this month, and if you’re wondering how to bridge assets to the new chain, we’ve got you covered.
Having an in-house decentralized bridge is the trick to getting ahead of the curve.
It helps blockchains not to be isolated from other networks within the space. Parallelly, enhances interoperability and boost the overall health of the ecosystem.
Most existing solutions compromise on either decentralization, security, or speed. Sonic’s native bridge to Ethereum, however, checks off all these boxes as a prerequisite.
The Sonic Gateway
Sonic’s native bridge — Sonic Gateway — facilitates ERC-20 token transfers between Ethereum and Sonic. There’s no master key, which means only the user will have access to and control over your funds on the bridge.
The bridge has not been launched as of the time of writing. However, it’s slated to go live soon. Once that happens, you can start bridging your assets.
Here’s how you can go about with it:
- Head over to gateway.soniclabs.com
- Connect your web3 wallet (The team recommends using Rabby)
- Choose the origin chain (Ethereum in this case) and the destination chain (Sonic)
- Pick the asset you wanna bridge and specify the number of tokens
- Check if you’re receiving the same amount on the other chain
- Approve the transaction
And that’s it! Your assets are now being bridged over.
Assets bridged through the Gateway are processed in intervals called heartbeats. This ticks the gas efficiency box as it makes sure many assets are bridged together.
From Ethereum to Sonic, there’s a heartbeat every ten minutes [which is obviously slower than solutions like Optimism but way better than others from the clan like Polygon].
Meanwhile, transfers from Sonic to Ethereum take up to one hour [Sonic is the pick of the litter here].
