The Mainsail team is actively working on refinements and enhancements to Mainsail EVM. This article examines the key changes, including the new block structure and tooling upgrades.
New Block Structure & Serialization Enhancements
One of the key changes is the addition of the **LogsBloom** field to blocks. This 256-byte data structure allows efficient checks to determine whether a block might contain specific log entries without scanning each one individually, significantly speeding up log lookups. Additionally, block gas calculation has been refined to sum only the actual gas used rather than transaction gas limits, providing a more accurate view of block consumption.
Dependency & Tooling Updates
Nearly all project dependencies have been updated to the latest stable versions. Importantly, **package versions** are now locked in production builds to ensure stability. Core development tools like **TypeScript** and **ESLint** have also received major updates, with necessary code adjustments made to accommodate new rules and breaking changes.
Enhancing Compatibility and EVM Handling
The EVM implementation now supports **multiple pending commits** at the same block height, which is especially useful when a block does not reach consensus in the first round. Additionally, legacy support for second signatures is being added, ensuring smoother migration paths as we plan to integrate data from the existing ARK network.
In the coming weeks, the Mainsail team plans to complete the remaining features needed to launch a new network that chains directly from the existing testnet. More developers and contributors are expected to join the Mainsail EVM testnet soon.
