All Categories

Development Progress | Züs Weekly Debrief  (March 30, 2022)

Chad Hanson
March 30, 2022
News & Updates
I hope everyone has been having a good week so far! We noticed the community has been enjoying the uptick in our Twitter presence. Make sure to keep liking, retweeting, and posting your own content. Keep your eyes open for more content coming soon! I will plan on breaking down weekly updates and development progress into further digestible content for the community in the coming weeks. This week, we take another look at development progress for both the blockchain and blobber networks, with the completion of some milestones. Let’s dive in:

Blockchain Development Progress

Over the course of the past week, the team address 7 main issues on the Züs repo and closed 15 PRs. They opened an additional 5 new PRs that they also plan to address. Among the closed PRs, the issues addressed included:

  • The team was able to fix a race condition on the blobber ReadMarker by changing the ReadCounter to ReadSize. This will help optimize the payment structure and business logic that occurs when a file or multiple files receive read requests. To learn more about the PR and associated PRs on other repos, click here.
  • The team uncovered a potential panic issue that was caused when estimating a transaction cost and were able to implement a fix. With a small change to the code, the team was able to address a bug that would occur upon unlocking stakepool. When certain scenarios arose, it would return improper data, causing issues upon attempting to unlock the staked tokens. Check here for more details. These are a couple of the smart contract fixes we have been referring to over the past week and are critical to ensure safe interactions with our network by users and service providers alike.

Development Progress

  • Other areas of improvement include the following. Fixes to make the APIs return 404 on unknown paths, instead of returning the diagnostic page, stopping the generation of challenges when there are no validators, as well as fixing a 0dns patch issue. Previously, the 0dns patch was stale so the team updated it in order to make it workable
  • Other smart contract progress has been made on the blobber block reward and challenge generation PRs. These are still under testing and an internal review by the team.
  • Notably, the highly discussed transaction nonce PR has made significant headway. This PR is very close to being merged since all the system tests have been fixed. Small issues arose during special case testing that needs to be addressed. This is being done in order for proper delegate wallet setup for service provider nodes.
  • We recently implemented a new PR to verify the integrity of the partial state acquired from remotes. This PR is coupled alongside several other PRs related to the partial state. The intent of these fixes is to validate the partial state to ensure that all nodes are connected to the network and can be reached from the root; a critical component for overall functionality and network security. It also checks if duplicate nodes are detected, which can be used to prevent malicious nodes which could fake the partial state if certain requirements/consensus is met. It is currently undergoing systems testing and will pass when fixed.
  • The final progress was on the linter errors fixing PR which successfully passed testing. To recap, this is to ensure our code is maintainable, easy to read, and update in the future. In doing so we are creating a standard across our code base.

Blobber Development Progress

Over the past week, the blobber dev team has closed 5 PRs, and 4 issues and opened 4 new PRs. During this time, they mainly updated the blobber to address batch uploading and to support our available after feature.

  • The blobber network was updated to support the uploading of a batch of chunks in one request. Previously, we split a large piece of data into a lot of small chunks which required us to send multiple HTTP requests to upload the data. Overall, this was an inefficient way to perform the tasks. So we were able to update the code which allows for the sending of multiple chunks of data in single requests. Check the details here.
  • They also finished the available-after feature implementation. This feature basically gives the user the capability to share resources with others. But it would only be viewable after a certain time. Meaning, if you wanted to share a data set starting at a certain period of time, you could set the availability of the data to occur at a specific date and time of your choosing.

About Züs

Züs is a high-performance storage platform that powers limitless applications. It’s a new way to earn passive income from storage.

Latest Articles
Tiago Souza
March 29, 2023

Tomorrow we will be hosting our Cloud Cover AMA (Ecclesia #12), so make sure to attend on Thursday, March 30, at 9 am PST as Saswata will be giving an update on Züs Mainnet and the ZüsApp demos!