Browse By

Introducing the ThunderCore Iris Hard Fork

The Iris hard fork will increase cross-chain compatibility to the ThunderCore blockchain, marking a new dawn for ecosystem expansion. What will it mean for developers?

Introducing ThunderCore Iris, the next iteration of the ThunderCore blockchain! The Iris hard fork will go live on Mainnet at block height 82312803.

The goal of this major network upgrade is to bring the latest EVM Istanbul features to ThunderCore and further lower the barrier of porting Solidity projects into the ThunderCore ecosystem. Iris complements the performance and security upgrade introduced in the Soter hard fork in December 2020. With the introduction of the Iris hard fork, ThunderCore will become one of the fastest, most secure, EVM-compatible, cross-chain ready,  and developer-friendly public blockchains in the industry!

Why Iris?

Iris is the Greek goddess of communication, messages, the rainbow, and new endeavors. Being represented as a rainbow or as a beautiful young maiden with wings on her shoulders, Iris is the perfect symbol that personifies our incoming hard fork, as the Iris hard fork is meant to bring better cross-chain interoperability to the ThunderCore blockchain, creating a more developer-friendly platform for great projects to scale.

 

Roadmap

The Iris hard fork will be introduced with a phased rollout:

Phase 1: Estimated date: 10/12, Block height: 82312803

During Phase 1 of the Iris hard fork, the goal is to introduce a limited set of changes to ensure the stability of the Phase 2 rollout. The upgrades include:

  1. Move consensus info from consensus transaction to block header

       Note: this should not require major updates to your codebase

  1. Limit the range of eth_getLogs queries to
    1. Testnet: approximately 2 days (2 * 86400 block) (toBlock – fromBlock)
    2. Mainnet: no limit

Note: the change will only affect the Testnet during Phase 1, developers should test the effects of the eth_getLogs change on Testnet during this period so as to prepare for the changes on Mainnet in Phase 2.

  1. Security upgrades

Phase 2: End of the year

During Phase 2 of the Iris hard fork, major upgrades to the ThunderCore blockchain will take place, including:

  1. The ThunderCore go client will be updated to be compatible with geth 1.10.8
  2. EVM opcode upgrades:
    1. EIP-1014: CREATE2

Note: add the CREATE2 opcode to allow interactions to be made with addresses that do not exist yet on-chain but can be relied on to only possibly eventually contain code that has been created by a particular piece of init code. This is very useful when porting Solidity smart contracts to ThunderCore, for example for state channels that involve counterfactual interactions with contracts.

  1. EIP-145: Bitwise shifting instructions in EVM – SHL, SHR and SAR

Note: add bitwise shifting operators in addition to the existing logical and arithmetic operators.

  1. EIP-1344: ChainID opcode

Note: add the CHAINID opcode to return the current chain’s EIP-155 unique identifier inside the smart contract for better cross-chain compatibility.

  1. Limit the range of eth_getLogs queries to
    1. Testnet: approximately 2 days (2 * 86400 block) (toBlock – fromBlock)
    2. Mainnet: approximately 2 days (2 * 86400 block) (toBlock – fromBlock)

Note: developers using eth_getLogs should update your Mainnet code accordingly.

The Iris hard fork brings better cross-chain compatibility to the ThunderCore blockchain thanks to the improved EVM compatibility. Combined with low gas fees, high throughput and industry-leading security, this makes ThunderCore an ideal Layer-1 chain to migrate your DeFi Dapp to. Get ready for never-before-seen Dapps and services on ThunderCore thanks to the Iris hard fork!

Follow us on:

Website: https://www.thundercore.com/

Twitter: https://twitter.com/ThunderProtocol

Medium: https://medium.com/thundercore

Telegram group channel: https://t.me/thunder_official

Telegram announcement channel: https://t.me/thundercore_announcements

Disclaimer: The views, suggestions, and opinions expressed here are the sole responsibility of the experts. No Real Prime News journalist was involved in the writing and production of this article.