Ontology Mainnet Upgrade to v3.1.2 on Aug. 21 Brings Four Ethereum EVM Features

Ontology, a decentralized AI knowledge infrastructure undertaking, has introduced a scheduled mainnet improve to model 3.1.2, set to take impact at block top 20,800,000, which is predicted to happen at 12:00 a.m. UTC on Aug. 21. The improve introduces 4 Ethereum Digital Machine (EVM) options aimed toward enhancing good contract effectivity and easing the migration of Ethereum-based code.

Key EVM Options Added

The improve will incorporate 4 opcodes and ideas from the most recent Ethereum surroundings into Ontology’s EVM: PUSH0, BASEFEE, MCOPY, and transient storage. These options are a part of Ethereum’s ongoing growth, significantly the Shanghai and Cancun upgrades, and are designed to optimize contract execution.

• PUSH0: Introduces a zero-cost opcode for pushing the worth 0 onto the stack, lowering contract dimension and gasoline prices for sure operations.
• BASEFEE: Permits good contracts to entry the bottom price of the present block, enabling extra dynamic price dealing with and higher integration with EIP-1559-style mechanisms.
• MCOPY: Offers a extra environment friendly option to copy reminiscence areas, reducing gasoline consumption for memory-heavy operations.
• Transient storage: Provides short-term storage that persists solely inside a transaction, providing cheaper options for sure use circumstances like reentrancy locks.

These additions are anticipated to scale back good contract dimension and a few computation prices, making it simpler for builders to port code written for the most recent Ethereum surroundings to Ontology. For initiatives constructing on Ontology, this might imply decrease deployment and execution charges, in addition to broader compatibility with Ethereum tooling.

Node Operator Motion Required

Node operators should replace their software program to v3.1.2 earlier than the community reaches block top 20,800,000 to use the improve. Failure to replace might lead to nodes falling out of sync with the upgraded chain, doubtlessly inflicting disruptions in block validation and transaction processing. The undertaking has urged operators to plan the improve forward of time to keep away from community instability.

Why This Issues for the Ecosystem

This improve displays a broader pattern amongst blockchain networks to align extra carefully with Ethereum’s requirements, given Ethereum’s dominant function in decentralized finance and good contract growth. By adopting these options, Ontology goals to scale back friction for builders who need to deploy cross-chain functions, doubtlessly growing its attractiveness as a platform for AI-related knowledge infrastructure. The transfer additionally underscores the significance of sustaining EVM compatibility as a strategic precedence for layer-1 networks in search of to faucet into the broader Ethereum ecosystem.

Conclusion

The Ontology mainnet improve to v3.1.2 is a technical however vital step ahead, bringing enhanced EVM capabilities that may decrease prices and enhance developer expertise. With node operators required to replace by Aug. 21, the profitable implementation will depend upon well timed coordination throughout the community. For customers and builders, the improve alerts Ontology’s dedication to staying aligned with Ethereum’s evolving requirements, doubtlessly opening new alternatives for cross-chain innovation.

FAQs

Q1: What’s the Ontology mainnet improve v3.1.2?
The improve introduces 4 Ethereum EVM options—PUSH0, BASEFEE, MCOPY, and transient storage—to enhance good contract effectivity and cut back prices. It’s scheduled to activate at block top 20,800,000 on Aug. 21.

Q2: How will the improve have an effect on good contract builders?
Builders will profit from diminished contract sizes and decrease gasoline prices for sure operations. Moreover, code written for the most recent Ethereum surroundings may be migrated extra simply to Ontology, simplifying cross-chain growth.

Q3: What do node operators have to do?
Node operators should replace their nodes to v3.1.2 earlier than the community reaches block top 20,800,000 to make sure they continue to be suitable with the upgraded chain. Failure to replace might result in synchronization points.