The BNB Smart Chain will go through a hard fork tomorrow. The upgrade will take place at around 08:00 AM (UTC) at block height 22,107,423. The changes are aimed at mitigating the cross-chain infrastructure between the Beacon Chain and the Smar Chain in an attempt to re-enable the cross-chain back. What is the BNB Smart Chain Moran Hard Fork? According to a release on Github, the BNB Smart Chain will go through a hard fork tomorrow – October 12th. The upgrade is called Moran, and it represents a “temporary urgent patch.” This release is a temporary urgent patch to mitigate the cross-chain infrastructure between Beacon Chain and Smart Chain so that the cross-chain can be re-enabled back. It is a hard fork release for both testnet and mainnet. The changes that Moran will
Topics:
George Georgiev considers the following as important: AA News, Binance, Binance Smart Chain
This could be interesting, too:
Andrew Throuvalas writes Bitcoin Maximalism Will Rise Over Time, Predicts Balaji
Chayanika Deka writes Latin American Fintech Giant Nubank Enables Bitcoin Withdrawals and Deposits: Report
Mandy Williams writes FTX to Auction Off Remaining Solana (SOL) Tokens: Report
Andrew Throuvalas writes Here’s The Exact Top Of The Next Bitcoin Cycle, Power Law Says
The BNB Smart Chain will go through a hard fork tomorrow. The upgrade will take place at around 08:00 AM (UTC) at block height 22,107,423.
The changes are aimed at mitigating the cross-chain infrastructure between the Beacon Chain and the Smar Chain in an attempt to re-enable the cross-chain back.
What is the BNB Smart Chain Moran Hard Fork?
According to a release on Github, the BNB Smart Chain will go through a hard fork tomorrow – October 12th.
The upgrade is called Moran, and it represents a “temporary urgent patch.”
This release is a temporary urgent patch to mitigate the cross-chain infrastructure between Beacon Chain and Smart Chain so that the cross-chain can be re-enabled back. It is a hard fork release for both testnet and mainnet.
The changes that Moran will bring to the network include a fix of the vulnerability in “the iavl hash check,” intended to eventually migrate it to ICS23 specifications. Additionally, it will introduce a block header in the sequence check in the CrossChain Contract.
Last but not least, the hard fork will also make the relater whitelisted to the genesis candidates. The Github entry also specifies that there will be further Binance Chain Evolution Proposals (BEPs) on how to define the candidates for the relayer.
What To Do?
Regular users needn’t do anything. However, node operators will have to take a few steps. First, they would have to download the binary contained in the Github entry.
After that, they would have to stop their node if it’s still running and replahardce the old binary with the new one. Once this is done, they will have to restart their node. That’s pretty much it.
It’s worth noting that the hard fork comes as a response to the vulnerabilities discovered after the most recent hack, where over $100 million worth of cryptocurrency was compromised.