Happy Wednesday everyone! For the next few weeks, I will be taking over for Chad on the weekly updates. Chad is really busy with his new job and deserves some free time. Big shout-out to him and all his effort and support throughout all these years! Before I get into the dev update and frontend APIs update let me introduce myself to any who do not know me.

My name is Tiago and I’ve been around since the start of the community; a true OG! I am excited to work as a bridge between the team and the community. Feel free to reach out to me on telegram if you have questions regarding the project. That said, let’s dive into this week’s update.

Last week, the dev team focused on supporting the new demos for our much anticipated apps. As we approach the premainnet events, demos are being finalized for you to experience the UI and new functionalities that you’ve all been patiently waiting for. This week’s update is rather technical and mainly focused on frontend APIs.

Development Team Updates

The blockchain team closed 17 PRs, which were mainly focused on frontend APIs to support the upcoming demos.

New frontend APIs were created and updated. frontend APIs were updated 1) to support getting block by round number and to list the latest transactions with pagination, 2) to update the allocation stats on event db, 3) to return total blobber reward, and 4) to return the rank of a blobber. By implementing support for these APIs, the team ensures that data streams that communicate information to our block explorer will provide accurate information in a timely fashion.

Further updates enabled cors and set allowed origin to all (set on nginx ingress) to allow more feature interaction via wasm. The team updated blobber validation processes which refactors the naming of code to make it easier to understand while implementing a min_write_price to ensure that allocation data, staking capacity, etc are accurate.

Blobber Selection

Furthermore, the team changed how blobbers are selected when creating allocations, and its allocation size is to be divided by DataShard, instead of DataShards + ParityShards, which is consistent with the blobber implementation. This will ensure the allocations are consistent with the current blobbers implementation. This also will trigger an update when staking to the pool is modified.

While conducting our series of intensive Byzantine tests, the team was able to discover a fault tolerance test issue that would prevent miners and sharders from syncing the transaction nonce after restarting. This results in the miners and sharders inability to create new transactions, generate blocks, etc, and subsequently fail the fault tolerant tests.

Moreover, they implemented the minimal lock period restriction to avoid the client’s lock and unlock tokens too frequently. With the Züs ecosystem enabling the ability for users to delegate tokens to service providers, read pools, or storage allocations, the team implemented a minimal period of time to prevent abuse of stake pools and prevent spamming of the network. The team continued its work to implement nonce management between conversions ZCN <-> WZCN for the upcoming bridge.

Blobber & gosdk

There were a few changes on the blobber side. Some PRs were closed on the gosdk, and others are currently being reviewed. These will be merged following the final rounds of testing.

The gosdk bridge smart contract was updated to decrease gas consumption and state size, effectively placing less strain on users and service providers. The team added a missing FactoryModuleERC721PackedAddress config to enable full functionality. Updates to gosdk were made in order to expose listAllocation on wasm and to expose other allocation-related APIs on wasm. They also added stake_at to support the min_lock_period feature implementation mentioned above.

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.