Züs Weekly Debrief May 31, 2023
Cloud Cover AMA:
Greetings, Züs community! Hope you are doing well. As a reminder, we have our forthcoming Cloud Cover AMA (Ecclesia #16) scheduled for Thursday, June 1st, at 9 am PST. Saswata will be offering the latest updates on Züs Mainnet, the Active Set and the Apps. This is an excellent occasion to keep up to date with our advancements and peek into what is in store. Do not forget to contribute your questions in our Discord channel or directly message me on Telegram.
Storm of the Week:
Recently, Züs was highlighted in a HackerNoon article “Will Decentralized Storage Challenge Mainstream Solutions?”. The article focused on the transformative potential of decentralized storage, addressing the increasing demand for data storage and the issues associated with centralized systems, such as, security vulnerabilities and privacy concerns.
In decentralized storage systems, data is distributed across a network of peer-to-peer nodes, ensuring no single entity has total control. This ensures data security and privacy. Moreover, decentralized storage provides more resilience, censorship resistance and more control over data to end users.
Furthermore, the article also explores several notable projects in the decentralized storage field, including Züs, Storj, Filecoin, and Sia. It provides a comparative table that highlights the key features and characteristics of these projects, allowing readers to make informed assessments.
Despite the advantages of decentralized storage systems, it is important to acknowledge the challenges they currently face. The article highlights a few of these hurdles, including technological complexity, potential network instability, and the need for broader adoption.
However, the potential benefits offered by decentralized storage systems are so substantial that they continue to garner significant attention and investment. Notably, projects like Züs are actively dedicated to overcoming these challenges and actively developing innovative solutions in this space.
Blockchain Updates:
Last week, the blockchain team primarily focused on closing issues and conducting code reviews to speed up the merging of PRs: 16 PRs were merged in the 0chain repo, 16 PRs in gosdk and 6 PRs in blobber repo. Additionally, the team successfully merged the PR that fixed the MPT stuck bug, enabling deployment in all test environments. The team also continued testing the future transaction limit and addressed load test errors in the /testnet. The following are the main issues that have been closed and are now ready for review:
- The team resolved the duplicate event issues identified in the previous week. The main issue was that the finalizing block process did not guarantee atomicity between the LFB state setting and the event process. This meant that events could be processed while the LFB state was not updated when the sharder stopped or encountered a panic, and vice versa. The fix ensures that failure on either side does not affect the other side. The solution has undergone thorough testing before merging. See details in PR.
- The team submitted a PR for the future transaction limit, which has been deployed to /testnet and subjected to load testing for a while. It is now ready to be merged.
- The team added the MaxTokenSupply constant and implemented validation when receiving submitted transactions, as well as when generating a block. This addition prevents panics (although they could be caught by the recovery mechanism) when processing events that involve transactions exceeding the int64 value. See the fix in the PR.
- To prevent malicious miners from generating duplicate built-in transactions, the team implemented a limitation on the number of such transactions. Further details about the issue can be found in the associated issue, and the fix is included in the aforementioned PR.
The following are the core PRs we merged in 0chain, gosdk and blobber repos:
0chain repo:
- Removal of getUserLockedTotal
- Fixing benchmarks for shutdown blobber and validator
- Adding missing benchmark tests, populating benchmark aggregate tables, and making the population of some event db tables more efficient
- Updating cost config based on the benchmark tests result
- Upgrading go to 1.20
- Fully ordering all event database pagination queries
- Fixing transaction errors
Gosdk repo:
- Fixing pending WM check
- Fixing jwt token error
- Adding remotepath in sync command
- Fixing duplicate WM
- Returning callback on success for DownloadFromBlobber
- Refactoring upload request
- Adding lock value int64 overflow checking
- Retrying submit WM if lock exists
- Exposing getRemoteFileMap
- Exposing allocation repair to wasm
Blobber repo:
In summary, it has been an exciting week for the Züs team. We were highlighted in a HackerNoon article and our team made great progress on issues and code reviews. Be sure to join us for our AMA tomorrow as we dive deeper into the Züs developments. Our team continues to tighten up code each week while working to ensure that security on our platform remains top of mind. Together, we can use decentralized storage to challenge traditional solutions. It is an exciting time for both technology and blockchain innovation.
