We’re excited to announce Monza, a massive upgrade to Movement.
Monza allows transactions to be submitted through third-party nodes and redesigns the data availability sequencer. The changes should resolve the network stability and latency issues, marking a leap forward for Movement’s many amazing builders and users.
Monza is a milestone for Movement’s decentralization and performance.
The upgrade is live now.
Latency Improvements
Movement’s latency has been cut from about 12 seconds to about 1 second. This drastic improvement results from reimagining the DA.
Formerly, transactions were rewritten within a block, then the block was written to Celestia, read back, and sent to the MoveVM. This was an asynchronous process, meaning the node had to wait 5 seconds for Celestia to create the block before execution. This process took too long.
With Monza, more happens simultaneously. Now, transactions are reordered within the DA light node, which writes the block to full node for parallel execution. Accepted batch transactions are added to the produced block. The node-DA connection has been optimized.
Full Node Upgrade
Before Monza, you could only submit transactions using the leader node. Now, you can use third-party nodes as well.
More options means greater decentralization and robustness. Because the network is far less reliant on the leader node, Movement should now have greater stability and consistency.
This will make Movement smoother and easier to use.
What to Know and Resources
Builders and users don’t need to take action.
However, node operators must take specific action.
Detailed instructions are posted in the dedicated Telegram channel.
Docs for running your full node can be found here.
Finally, for a deeper dive into Monza, see this GitHub issue.