Beware of Scams | Züs Weekly Debrief May 17, 2023
Cloud Cover AMA:
Hello, Züs community! We hope you are having a great week so far. Just a friendly reminder our upcoming Cloud Cover AMA (Ecclesia #15), taking place on Thursday, May 18th, at 9 am PST. Join us, as Saswata provides updates on Züs Mainnet and our Apps. This is a fantastic opportunity to stay informed about our progress and get a glimpse of what the future holds. Remember to share your questions in our Discord channel or send them directly to me on Telegram. In this update, we discuss the current blockchain updates, as well as how to beware of scams.
Now, let’s dive into the latest weekly update!
Beware of Scams:
We want to bring your attention to a concerning matter regarding scam accounts impersonating Züs team members. With any new development in this space comes an increased risk of scams — but do not worry! It is crucial to remain cautious and vigilant to protect yourself from potential fraud.
Please note the following:
- There is no token migration taking place currently, and there are no plans for it in the future.
- Our official Admins will never initiate a private message (PM) with you first. Be cautious of unsolicited messages claiming to be from Züs Admins.
- Züs Admins will never ask for your wallet address, request transactions, or solicit any personal information. Protect your privacy and avoid sharing sensitive details.
- Be aware of scammers adding you to fake Telegram groups. Exercise caution and verify information through our Announcements Channel.
- Don’t forget to join our newsletter to receive weekly updates and stay informed about the latest developments. Sign up here: https://zus.network/
Blockchain Updates:
In the past week, the blockchain team continued investigating the MPT bug. Based on the status of the Testnet network, we are confident the MPT bug has been resolved. The network ran smoothly for a week without encountering any state hash mismatch errors or missing values in the partitions. We will keep monitoring the network.
The main issue revolved around the MPT node, which underwent unexpected changes after being saved to memoryDB. To prevent potential alterations, the team implemented a fix that involved saving a cloned value of the node instead of a direct pointer to the memoryDB. Additionally, the team identified a bug within the partitions themselves, specifically relating to the removal of items. By addressing these two issues, the network operated significantly better.
Load Tests
Aside from addressing the MPT bug, the team also resolved several issues related to load tests. Previously, the tests failed to treat transaction chargeable errors as errors, resulting in cases appearing passed even when they had actually failed. Certain cases depended on the success of other transactions, and if those transactions failed but were mistakenly considered successful, the tests would become stuck and wait for an extended timeout period.
Another challenge encountered on the testnet was the slow processing of transactions. The team noticed an accumulation of over 10,000 transactions in the transaction pool, whereas most generated blocks only contained two built-in transactions. This indicated that the network struggled to include any transactions from the pool. The team conducted investigations and performed experiments to enhance the situation. They focused on removing invalid future transactions, although distinguishing these from valid future transactions proved challenging. As clients could concurrently submit transactions by incrementing the nonce sequentially, any failed transaction rendered subsequent transactions invalid. However, there was a risk of mistakenly removing valid future transactions.
Closed PRs
Additionally, the team successfully closed 12 pull requests (PRs) in the 0chain repository, 10 PRs in gosdk, and 10 PRs in blobbers. Here are the details of the closed PRs:
- Fixed the writemarker redeem issue, ensuring that no error is returned when there is no record in the challenge ready partition
- Corrected ZCN add to the delegate pool by retrieving settings from the configuration file rather than MPT.
- Updated blobber.saved_data and blobber.allocated after canceling an allocation.
- Fixed benchmark errors.
- Fixed a corner case related to calculating user aggregates.
- Resolved a panic issue in the transaction event.
- Enabled s3 tests and fixed s3 build.
- Ensured that only the blobber or validator wallet can shut down a blobber or validator.
- Fixed processed challenges.
- Exposed EstimateFee to the mobile SDK.
- Exposed a multi operation to the mobile SDK.
- Returned proper error when deleting a file.
- Implemented the download from a single blobber feature.
- Fixed empty ID issue. New files should use the fileID of the old file.
- Disabled private sharing for unencrypted files.
- Fixed GetFileMetaFromAuthTicket and DownloadFromAuthTicket.
- Enabled the blobber to upload multiple files.
- Implemented commit synchronization.
- Added wallet files for blobber and validator.
- Executed challenges in order of block number.
- Fixed challenge and allocation numbers.
Tune in Tomorrow
All in all, the Züs network has a lot of exciting news coming up over the next few months, and we look forward to sharing more with you as time goes on. It is important to remember that we have our AMA tomorrow at 9 am PST, set your notifications now. Finally, it is very important to beware of scams. Although these experiences are becoming rarer and rarer thanks to our safety protocols, users should still be aware they could be at risk when dealing with someone online. We thank everyone for their support and enthusiasm thus far, and cannot wait to show you everything we have been working on diligently.
