Latest Protocol Releases

Greetings, MultiversX Builders! The Sirius Release (rc/v1.6.7) is officially live, marking a significant milestone in our roadmap. This release introduces over 18 new features, several critical breaking changes, and numerous fixes and improvements. It sets the stage for the upcoming Vega Release and paves the way for our goal of reducing finality time to 3 seconds.

🔧 Key Highlights:

• Multikey Support (#4741): Enhances node functionality by allowing them to sign with multiple keys, boosting security and flexibility in operations.
• Consensus Signature Check Optimization (#4467): Major CPU efficiency improvements in block signature verification during consensus, reducing processing time significantly.
• Governance v3 Contract (#4879): Introduction of a new governance contract in Go, running alongside existing system SCs, offering refined proposal and voting mechanisms.
• DNS v2 (#5045): An update to the DNS functionality, allowing multiple and deletable user names, managed through specialized smart contracts.
• Balance Data Tries (#4636): In the data trie, values are now saved at the hash of the key instead of the original key, ensuring a balanced structure by randomizing the keys. A 'Version' field is added for backward compatibility, and a new API endpoint confirms if an account's data trie is fully migrated.
• VM1.5 (#4789): Integration of the new smart contract processor with features like Multi-async, ManagedBigFloats, ManagedMap, BackTransfers, and updated to Wasmer 2.2.
• Transaction Execution Ordering Refactor (#4918): Redesigns the grouping and execution order of transactions for improved efficiency and reliability in cross-shard interactions.
• Dynamic Gas Cost Introduction(#749): This change addresses a previously unnoticed imbalance—the time consumed for accessing the trie wasn't reflected in transaction consumed gas.

We've covered these updates in our recent developer sessions on Discord. To ensure a seamless transition, we encourage all developers to review the changes outlined below and prepare accordingly before January 16th. For support, queries, or further clarifications, reach out to us on Telegram, Discord, or your preferred communication channel.

Events notifier release v1.2.0+ has to be synced with mx-chain-go Sirius release:

• There is a new observer node → notifier integration using WebSockets.
• Outport data refactoring to common structures for all outport drivers. The same data that is sent to other drivers (like indexer) will be now sent to notifier. The already existing data events will be backwards compatible, they will not be changed.

Builders of MultiversX,

A simple yet important hotfix was needed for fixing the senders filter.

Send us feedback and let’s get in touch if you have any improvement ideas. Become a builder!

The v1.3.0 release of the mx-api-service by MultiversX brings a comprehensive set of new features, bug fixes, and other notable changes aimed at enhancing the functionality, reliability, and performance of the service. Some of the most important features are:

• Node sync progress percentage.
• Apply price & marketCap for Hatom tokens.
• Sovereign shards support as seen at xDay 2023.

Send us feedback and let’s get in touch if you have any improvement ideas. Become a builder!

• Replicated VM 1.5 in the Rust VM. This includes support for:
• promises,
• back-transfers,
• modified event logs.
• New endpoint annotation, `#[upgrade]`. Contract variants with upgrade endpoint, but without init now allowed.
• Build system:
• `wasm` crates now fully generated based on data from `sc-config.toml` and root `Cargo.toml`.
• Setting wasm target dir automatically, if not specified, based on workspace.
• Better hygiene in codec derive.

Calling all Validators!

We're rolling out a new upgrade for your nodes! This release introduces:

• An important fix for nodes starting an epoch in a new shard without recent DB info. This is necessary for shuffled-out validator nodes.

This enhancement ensures smooth state synchronization, even when a setGuardian transaction occurs at the epoch change. As always, ensure you're using the right Go compiler version (v1.20.7). Happy upgrading, and don't forget to join our Discord community for discussions, support, and sharing innovative ideas.