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

Vetiver 9.0.4: Patch Release

Vetiver 9.0.4: Patch Release

Vetiver 9.0.4 addresses several reported issues, including fixes for the Import Sync feature and the eth_estimateGas RPC method, along with security, performance, and reliability improvements. Although this is not a mandatory release, we recommend that node operators upgrade to this version to benefit from the improvements it introduces. The latest version of the RSKj client […]

Ecosystem Updates
Parallel Transaction Execution: Why Blockchain Needs to Learn to Multitask

Parallel Transaction Execution: Why Blockchain Needs to Learn to Multitask

As blockchain networks continue to mature, the conversation around scalability is changing. For years, the focus has largely been on increasing throughput and reducing transaction costs. Those metrics still matter, but they don’t tell the full story of what it takes to support applications at scale. Today’s blockchain networks are expected to support a much […]

Fundamentals
Introducing Union Bridge on Testnet: Verifiable Bitcoin Bridging Begins

Introducing Union Bridge on Testnet: Verifiable Bitcoin Bridging Begins

Now live on Rootstock Testnet, Union introduces a new model for Bitcoin interoperability based on verification rather than trust. By strengthening the security assumptions behind how BTC moves into programmable environments, Union reinforces Rootstock’s role as the Bitcoin-aligned smart contract platform. This first release is experimental and not production-ready, but it lays the foundation for […]

Ecosystem Updates