Introducing the Lucas (v.2.6.2) Upgrade
Introducing the Lucas (v.2.6.2) Upgrade
Faster transaction confirmation and more
Key Points
Introducing the Lucas (v.2.6.2) upgrade and the Shilin hardfork on Ronin mainnet! After this release, users will find their transactions confirm much faster than before.
We are also deploying REP-0002, which will improve security and make future Ronin updates more efficient.
The Shillin hardfork is scheduled to take place at block 28825400. If you’re running a validator or an RPC node on mainnet, please upgrade to Lucas before October 26th.
Today, we’re thrilled to introduce the Lucas (v2.6.2) upgrade and the Shillin hardfork on the Ronin mainnet! The Lucas release also encompasses REP-0003 and REP-0002. We’ll describe these in more detail below. If you are running a validator or an RPC node on the mainnet, please upgrade to Lucas before October 26th. Here’s everything you need to know:
Shillin Hardfork and Two REPs
Ronin has always been a blockchain for gamers, and we know that gamers appreciate having the fastest transaction confirmations they can get. That’s why we’re excited to release the Shillin hardfork and REP-0003: Optimistic Fast Finality. Together, these will reduce the time it takes to finalize a block on Ronin from 45 seconds to 6 seconds. That means users will find their transactions are confirmed much faster than before!
Learn more about REP-0003 here.
In this release, we’re also deploying REP-0002 to reinforce Ronin’s security and make future updates more efficient. REP-0002 moves the Ronin Bridge into a standalone application, which simplifies Ronin’s consensus code. It also means future Ronin updates will take less time and effort, while reducing the risk of certain security vulnerabilities.
Learn more about REP-0002 here.
Final Thoughts
The Shillin hardfork is scheduled to take place at block 28825400 (Thursday, October 26, 7:00 UTC). If you are running a validator or an RPC node on the mainnet, please upgrade to Lucas before October 26th. Read more about Lucas (v2.6.2.) at the link below.