Welcome to the latest edition of Züs’ blockchain and Mainnet weekly update! We will take a look at all the updates that have been happening over this past week. We will also discuss why printing security is so important for keeping your systems safe, plus check out our review of the top five alternatives for Amazon S3 Web service that you should keep an eye on. Let’s get started!
We currently have 12 pull requests (PRs) under review and 13 issues in progress. The remaining 40 issues are minor and mainly related to gosdk, 0box, and system tests. We anticipate resolving these issues within a few weeks. Our load testing is progressing smoothly, and we plan to test all applications simultaneously to evaluate their performance.
Additionally, we have made significant progress in addressing the critical MPT bug. We can now reproduce the bug in just one day, compared to several days previously. As a result, we anticipate resolving the issue soon.
Our mobile and desktop Apps for Bolt and Vult will be available on the app store within the next two weeks. After that, users will be able to seamlessly switch to the live network on Mainnet. The stability of our web applications has also improved, with only a few remaining changes required for Blimp and Chimney in the next few days.
Storm of the Week:
The Importance of Printing Security:
In today’s digital age, printers and, multifunction devices are frequent targets for cyber-attacks, making it crucial for businesses to take proactive measures to secure their printing infrastructure. As Saswata Basu, the CEO of Züs, highlights in a recent article in DPS Magazine, “If the cloud is hacked or breached, malicious and false content can be printed and delivered to the people. False information could be hidden in the content body without being noticeable, and no one will suspect a data breach”.
Decentralized storage systems offer a promising alternative to centralized cloud storage as they provide increased security and resilience against cyber-attacks while enabling businesses to have better control over their data. By distributing data across a decentralized network, businesses can protect their data against cyber-attacks, including those targeting printers connected to decentralized storage systems.
Moreover, with encryption and smart contracts, decentralized storage can prevent unauthorized access, providing secure and private data storage environments. Additionally, they can offer increased resilience against cyber attacks as data is distributed across a network of nodes, rather than a centralized server.
As businesses increasingly adopt decentralized storage systems, it is essential to prioritize printing security within their cybersecurity strategies. By implementing secure printing solutions, access controls, and regular updates, and using decentralized storage solutions that prioritize security and privacy, businesses can protect their data and systems from potential cyber-attacks while controlling their data better.
Last week, the blockchain team focused on debugging the MPT issue while fixing load test issues. The good news is that progress is being made in fixing the MPT issue. Just yesterday, it was discovered that the MPT nodes had changed unexpectedly, which led to the value stored in a specified path being unable to be found. The nodes of those miners who could find the value were not changed. This is definitely a bug in MPT, so more logs were added to track the place where the node could be changed.
Before deploying the code, the team located one place in merging state changes that could change the node and lead to key != node.GetKey(). The places for syncing nodes from remote and syncing block states from remote were also examined. They should have validated the nodes, so they may not affect the MPT. The team will monitor the logs over the next few days to get closer to fixing the MPT bug.
Dev team is fixing load test errors
In the meantime, the dev team is fixing load test errors, which helped speed up the reproduction of the MPT bug. Previously, they needed to wait about two days before encountering the MPT issue, but now it can be seen in about 3-4 hours, and it may be even faster if they do load tests frequently. The main issues fixed in the load tests are:
- Insufficient transaction fee errors on submitting txns have been fixed.
- Insufficient balance to pay transaction errors on submitting txns have been fixed.
- Failed to send transactions due to incorrect miner state has been fixed. This fix is in the 0chain miner end. Miners will return an insufficient balance to pay the fee if they detect that the client does not have sufficient balance to pay the fee. However, they check the LFB to get the balance, so if the client pours tokens in round 100, but LFB is in 99, the miner will return an insufficient balance error. To fix this issue, they will only examine the client’s balance when the client’s nonce + 1 equals the transaction nonce. Otherwise, they would just let the transaction pass through.
- More filter cases for submitting transaction errors have been added, such as connection is reset by peer, resp_is_500, EOF.
- Cancel_allocation cases have been added to trigger allocation removal from blobber cases. They also stopped creating an allocation with full blobbers to have a spare blobber for updating allocation to add and remove blobbers. These can also trigger the remove allocation from the blobber.
In addition to debugging and locating the MPT issue, the team closed 26 PRs on the 0chain repository. These included:
- Saved rewards only if the miner existed in the network.
- Fixed the mint nonce overwrite issue.
- Merged transactions with the same hash when writing to event DB.
- Moved view-change tests.
- Fixed negative open challenges in the event DB.
- Fixed a nil pointer error during authorizers retrieval request.
- Fixed a broken pool table.
- Filtered getBlobbers and getValidators for is_killed and is_shutdown.
- Integrated smoke tests.
- Captured all errors on transactions.
- Updated the initial states file for blobbers and validators.
- Fixed a unit testing script failing to run 0chain.net/smartcontract/dbs/event tests.
- Added new metrics state and events computation times.
- Fixed/handled kill shutdown for aggregates and snapshots.
- Completed tokenomics suite.
- Added txn fee table.
Read Züs’ most recent article:
Check out our latest Züs Network blog post for a list of the top 5 AWS S3 alternatives. Companies in need of more space for data storage should keep an eye out for new technologies in the sector, like Züs, as these could be more efficient and cost-effective ways of managing and storing files over the long-term. By making an informed decision about their storage management system, organizations can ensure their data is secure and properly used.