Skip to content
Back to Blog
Ecosystem Updates

RSK and the Ethereum Merge

Read Time: 1 mins
RSK and the Ethereum Merge

“The Merge” is an upgrade to the Ethereum network that transitions from the existing Proof of Work (PoW) consensus mechanism to a Proof of Stake (PoS) mechanism. As an EVM-compatible chain, this transition affects the RSK network. Most notably, the RSK-ETH token bridge.

The RSK-ETH token Bridge allows users to easily move ERC20 tokens between the Ethereum and RSK networks. The exchange of tokens works through a bridge smart contract on each network. The bridge contract receives and locks the ERC20 tokens on one chain and then creates an ‘event’ that is sent to the bridge contract on the other chain. 

How does The Merge affect the RSK-ETH token bridge?

The Merge is Ethereum’s transition from PoW to PoS; however, post-merge, the ‘old’ PoW chain still exists in some form. It is up to the node operators to update their clients to support the new PoS chain.

At the time of writing, all nodes RSK-ETH bridge have been updated and configured to support the new PoS chain. The main difference post-merge is that the client used to run some of the nodes can no longer run a full ETH node on its own. However, by coupling such clients with “consensus client” software, the nodes were able to remain fully functional, and the transition was smoothly executed, with the bridge now fully operational for users.

Are my tokens stuck on the other chain if I bridged them before the Merge?

No, all tokens bridged from Ethereum to RSK and vice versa can be bridged back and forth between chains in the same way they were before. The only difference is now, when bridging from RSK to Ethereum the tokens you receive will be running on the new PoS chain!

Conclusion

The RSK network as a whole is mostly unaffected by Ethereum’s Merge. The only notable issue to address was the new configurations to the client nodes for the RSK-ETH bridge — all of which have been successfully implemented with minimal downtime. The same functionalities for the bridge have been retained, and users should see no difference in overall usability!

Recommended articles

Can AI Build a Second Rootstock Client? Lessons from a Rust Experiment

Can AI Build a Second Rootstock Client? Lessons from a Rust Experiment

Disclaimer: rustock is a personal experiment exploring how far today’s AI coding tools can go. It is not an official Rootstock client, has not been security reviewed, and should never be used in production.   One of the biggest long-term challenges for any blockchain is client diversity. Independent implementations make networks more resilient by reducing […]

Research & Innovation
Bitcoin Miners Can Now Directly Participate in Rootstock Merge Mining Through DMND

Bitcoin Miners Can Now Directly Participate in Rootstock Merge Mining Through DMND

For the first time, Bitcoin miners can directly control their own Rootstock merge-mining commitments and receive rBTC rewards to their own address through DMND, a Stratum V2-first Bitcoin mining pool focused on miner sovereignty and decentralized mining infrastructure. Announced today by DMND and RootstockLabs, this marks a major evolution in Bitcoin mining infrastructure and an […]

Ecosystem Updates
Aori Integrates with Rootstock to Unlock Cross-Chain Bitcoin DeFi

Aori Integrates with Rootstock to Unlock Cross-Chain Bitcoin DeFi

The Bitcoin DeFi ecosystem continues to grow as new infrastructure connects it to the broader decentralized finance landscape. A new integration is now making it easier for users to move capital across chains while accessing Bitcoin-based financial applications. Aori is now live on Rootstock, introducing its intent settlement protocol to the Bitcoin smart contract ecosystem. […]

Ecosystem Updates