At Mazze, we believe that a thriving community is the heart of any successful blockchain project. Over the past weeks, you’ve shared with us a variety of insightful questions that highlight your enthusiasm and commitment to our shared vision. We’re excited to present these questions and our responses, reinforcing our dedication to transparency and open dialogue.
Putting the community first isn’t just a slogan for us — it’s a guiding principle. We aim to make Mazze a project shaped by and for its community. By addressing your queries directly, we hope to create a stronger connection and ensure that Mazze continues to grow as a community-oriented initiative where every voice matters.
1. Technical side, what are the major differences from CFX? As far as I see from the github repo, the scripts are identical excluding some parameters/configs.
Although there might be some similarities in scripting because of shared best practices in blockchain development, Mazze introduces important differences that distinguish it from Conflux. The most notable difference is our consensus mechanism: Mazze uses a pure PoW approach with the RandomX algorithm, while Conflux relies on a hybrid PoS/PoW model with the Octopus algorithm.
Mazze’s choice of RandomX brings distinct advantages. Since RandomX is designed to be CPU-friendly, it supports greater decentralization by allowing more participants to mine using standard hardware, without needing specialized ASICs. This helps improve network security by spreading mining power more widely and encourages a more inclusive mining community.
For example, because Mazze uses RandomX, anyone with a standard CPU can participate in the mining process and help support the network, making it more accessible than systems that require costly, specialized equipment. This inclusivity gives more users the opportunity to contribute, aligning with our goal of a truly decentralized and open blockchain platform.
Also, Mazze is built to optimize transaction speed and reduce delays, resulting in quicker and more efficient transactions. We also want to make improvements in community involvement to create a more collaborative and user-centric environment.
2. According to the team, MAZZE uses POW scheme with RandomX algorithm. But I still see the POS scripts included in the repo. Any reason why this is happening?
As Mazze took its first steps, leveraging existing open-source foundations was a strategic move to gain momentum. Notably, although the project’s foundation is the RandomX algorithm within a PoW framework, remnants of an earlier approach that combined PoW with PoS, now dormant, still remain in the repository. Driven by the desire for community engagement, our immediate focus was on swiftly deploying the devnet, inviting users to explore, test and share their feedback. Our development cycle is now focused on carefully refining the code, with the systematic removal of these inactive PoS elements being a main goal.
3. What are the differences between the devnet we tested for almost a month and that is running currently and lauched last week?
Based on the feedback and findings from our initial testing phase, we’ve made several updates to improve the stability and performance of the Mazze network. For example, one of the main issues we encountered was related to the consensus mechanism, which caused the network to experience more forks than expected. This problem was partly linked to the configuration and startup process of the nodes.
We’ve also introduced a number of improvements over the previous devnet version. These include support for Mazze addresses in base32 format, which makes addresses easier to read and reduces the likelihood of errors when sharing them. Additionally, we’ve shortened the block time, allowing for quicker transaction confirmations and a more seamless user experience. These changes are part of our ongoing efforts to fine-tune the network and make it more efficient for everyone.
4. What projects/components are the team members mostly busy with? We only see some parameter changes from the recent github repo update, which shouldn’t take that long or cost so much labor.
We’ve recently finished a custom blockchain indexer, which plays a key role in enabling efficient data retrieval and processing across the network. This indexer serves as the foundation for various applications and services that depend on timely and accurate blockchain data.
We’re also in the final stages of preparing our first fully functional blockchain explorer (built from scratch), which is expected to go live in the next few days. The explorer will offer an easy-to-use interface for accessing real-time information on transactions, blocks and network statistics, improving transparency and user interaction with the Mazze blockchain.
Simultaneously, we’re dedicating significant efforts to fine-tuning our consensus mechanism. Optimizing this system is a complex undertaking that involves thorough research and development to maintain network security, scalability and performance. This work is vital for supporting future features and keeping the Mazze network strong and reliable.
5. Why did you adopt the plan to develop a new web wallet instead of using the existing replacement such as FoxWallet?
We opted to create a new web wallet to give our users a personalized experience of the Mazze blockchain. Although existing wallets like FoxWallet are open-source and perform well, building our own solution allows us to incorporate features and optimizations tailored specifically for Mazze. This gives us the freedom to introduce new functionalities that improve usability, security and the overall experience.
For example, our custom wallet can natively support the dual-layer structure of our blockchain, both the DAG and EVM layers smoothly. This all-in-one approach simplifies blockchain interactions and makes the platform more user-friendly.
The same for the blockchain explorer, tools like Blockscout were important during our initial development. However, we found that some components didn’t fully align with our DAG-EVM structure. Instead of maintaining separate explorers for each layer, which could complicate the user experience, we decided to build our own from the ground up. This enables us to deliver a unified view of the blockchain, allowing users to easily explore transactions and blocks across both layers.
6. The community wants a clear timeline for the explorer/fully-functional wallet/devnet campaign. Can we have such timeline, or at least for some of them? Investors lost confidence due to this as well. If a fully-equipped devnet cannot come out in October, it’s hard to believe that those things on the to-do list for Q4 could be completed on time.
Developing these important components is a complex process and while we aim to provide accurate estimates, unexpected challenges can sometimes lead to adjustments in our schedule. Even major projects like Ethereum have encountered delays during significant updates due to the complexities involved (for example the shift from PoW to PoS was delayed over 3 years!).
Our team has been working hard to navigate these challenges and we’re glad to share that both the explorer and the web wallet are now in the final stages of development, expecting to make them available in the next few days. Our focus is on ensuring that these tools are secure, reliable and meet the standards our community anticipates.
7. We need some improvements on the communication between the team and the community.
We want to keep the community engaged and informed and we recognize that the latest update may not have met your expectations.
We are actively working to complete the devnet, which will include an explorer and a fully functional wallet. The initial release was meant to share our progress, but we admit that providing only a screenshot without accessible tools fell short.
Our priority has been to ensure the stability and security of the core network before rolling out additional features for public use.
Going forward, we will make an effort to provide more detailed updates and clearer timelines. We are committed to seeing things from the community’s perspective and delivering results that are both meaningful and accessible.
8. Would you consider tapping into the expertise available within the community? If involving in development is a concern, appropriate community members could be used for vulnerability or reliability testing for example. This would help strengthen the concept of “community-oriented project”.
Yes, we are very interested in tapping into the expertise within our community. We understand that involving community members can significantly improve the development process, especially in areas like vulnerability and reliability testing, but not only. To support this, we are planning to introduce initiatives such as a community testing program, where members can help spot potential issues and share valuable feedback. For instance, participants might contribute by testing new features in a controlled setting and reporting any bugs or suggestions for improvement. This collaborative approach could not only helps us strengthen the security and resilience of Mazze but also builds a stronger connection with our community. By working together, we hope to build a platform that genuinely reflects the needs and insights of our users, reinforcing our dedication to being a community-centered project.
9. Any update on the Twitter Gold Badge? If it does not come back soon, is it possible to share with the community how your communication with the twitter team goes?
Currently, we have the blue checkmark, which disappeared temporarily without explanation. We’ve been in continuous communication with the Twitter support team to address the situation with the gold badge. While their responses haven’t provided clear guidance yet, we’re actively working to resolve this issue. Twitter has been updating their verification policies recently, which might be contributing to the delay. We will keep you informed of any developments.
10. What is the status of collaborations/partnership? Any projects we are collaborating on the node recruitment?
All of our previously announced collaborations remain active. In blockchain development, timing and coordination play a key role. Our partners are prepared to make significant contributions as we reach important milestones where their expertise will be most valuable.We’re also pleased to share that larger entities such as Ankr and Uphold have shown interest in Mazze. While we can’t provide further details at the moment, we’re optimistic that their involvement could bring considerable benefits to our community.
