The combined effect of these updates is a more reliable network. Nodes are less likely to fail unexpectedly, recover more effectively when issues occur, and provide a stronger foundation for future development.
The goal of these recent updates is to make the infrastructure more stable, reliable, and production-ready.
Stay with us now.
The exciting part is yet to come
๐ธ Major Codebase Cleanup
- Removed large amounts of legacy and unused code
- Simplified parts of the codebase
- Reduced technical debt
- Improved maintainability for future development
What this means: A significant amount of old, unnecessary, and unused code has been removed. While this may not sound exciting, it is one of the most important parts of maintaining healthy infrastructure. Cleaner code means fewer bugs, easier maintenance, and a stronger foundation for future development.
Happy June, Mazzians! ๐
While it may have looked like things were moving slowly, work has been happening behind the scenes.
Progress may not be at the pace we initially hoped for or what the community expects, but we are moving forward. Step by step, update by update, we are getting closer to the future we envision. Being as transparent as we are
Over the past few weeks, we have continued pushing updates to our GitHub repository, giving anyone interested the opportunity to follow development as it happens and even test the chain locally.
We have also been working on something beyond the code.
A new look and feel. One that better reflects where we are headed, and the long-term vision we are building toward.
There is still work to do, but progress is real, and we are excited to share more with you in the weeks ahead.
In Web3, there is often pressure to move fast, ship fast, and launch fast. But when you are building infrastructure, speed alone is not the goal. Stability matters more.
Moving fast can create excitement, but stability is what builds trust and making sure the foundation can hold. A network can only scale if it is reliable. Builders can only depend on it if it performs consistently.
That is why we take testing seriously. Why we run resets. Why we simulate different scenarios. Why we make fixes before calling something ready.
From the outside, that can sometimes look slow. To us, it is responsible building.
Infrastructure is not about who launches first. It is about what endures.
We would rather take the time to build something resilient than rush out something fragile.
Stability sustains ecosystems.
And in the long run, the projects that last are often the ones that choose to build right.
This is why we build, with stability in mind.
In todayโs digital world, we share more data than ever before. From payments to identity, much of our lives now exist online. Naturally, people are beginning to ask an important question. Who really controls that data?
This is why decentralization and privacy are becoming more important in todayโs marketplace.
Decentralization shifts control away from a few centralized entities and spreads it across a network. This reduces the risks that come with relying on a single authority. It also creates a more transparent environment where users are not left in the dark.
Privacy builds on that idea. It allows users to decide what they share and when they share it. Instead of handing over everything, people can interact digitally while keeping control of their information.
Together, decentralization and privacy create something powerful. They build trust. And trust is becoming one of the most valuable assets in the digital economy.
This is the thinking behind MAZZE.
MAZZE is designed as decentralized infrastructure for real-world applications. Security is built into the foundation. Transparency is part of the system. Privacy is considered from the start.
As the marketplace continues to evolve, the platforms that prioritize decentralization and privacy will be the ones that last.
That is the direction $MAZZE is building toward.
We are currently undergoing rigorous testing across the network to ensure stability, reliability, and performance. While things may appear quiet from the outside, a significant amount of work is happening behind the scenes.
These tests are necessary to simulate different scenarios, identify edge cases, and refine the system before the next stage. Our focus is not just on launching, but on launching something solid and dependable.
Progress may sometimes look like silence, but this phase is critical. Every test brings us closer to a stronger, more resilient MAZZE network.
We appreciate your patience as we focus on getting things right.
We will be back with more updates soon.
Following the latest update, we wiped and restarted the test chain multiple times to simulate different scenarios and further strengthen network stability. These resets were intentional and part of our final testing phase to ensure the system performs reliably under varying conditions.
Alongside this, we implemented several significant improvements to the codebase. Sync has been upgraded to protocol v4, introducing support for snapshot and epoch-hash messaging. This upgrade improves request and response validation, enhances local database header recovery, and smooths catch-up phase transitions.
We have also strengthened snapshot and state-sync error handling to improve resilience during synchronization. In addition, several consensus and txpool panic paths have been removed, reducing the risk of unexpected failures.
RPC transaction submission has also been improved. Invalid internal states will now fail explicitly rather than returning a false or misleading success response, ensuring more accurate and predictable behavior.
These updates represent another step toward a more stable, reliable, and production-ready MAZZE network.
We understand that at times it may have seemed like progress was slow. However, we have remained transparent about our situation and the work happening behind the scenes.
Development has been ongoing, and one of the most important things to highlight is this: you can now launch and test the MAZZE chain locally.
Updates to the node have been consistently pushed to GitHub, and they are publicly verifiable. This means you do not have to wait for announcements or releases to see progress. You can run the chain yourself and test how things are evolving in real time.
๐https://t.co/k3H96ZzsqA
We invite builders, contributors, and curious community members to:
โข Launch the MAZZE chain locally
โข Create and experiment with your own testing environment
โข Provide feedback
This is an opportunity to be part of the process, not just observe it.
This is just the first iteration, with deeper integrations and expanded capabilities already planned.
It is also important to note that mazze-agent is a side project and is not slowing down core development. Work on the MAZZE node and core infrastructure continues at full pace, while this tool is being developed in parallel to enhance the broader ecosystem.
We are excited to see how we've evolved up till this moment. More updates soon.
ICYMI: We released a new tool: https://t.co/T83wOBV2Gn
We know many of you use AI daily, and this tool is designed to help your "Lobster" better understand and interact with the MAZZE ecosystem. It opens the door for more intelligent interactions, automation, and experimentation within the network.
There are still a few fixes to finalize, but we are pleased to share that there are currently no critical bugs in the node. The network has undergone extensive testing across multiple scenarios to ensure stability and reliability.
This is why we are encouraging the community to start exploring. You can launch the MAZZE blockchain locally, create your own environment, and begin testing features firsthand. For those who prefer a shared setup, you are also welcome to join us as we continue testing together.
We will still be performing a few resets in the coming days as we refine the environment and finalize improvements. These resets are part of the final polishing phase as we prepare for the next stage.
We appreciate everyone who has been testing and contributing feedback.