Happy Wednesday! This week, as our development team works hard to ensure a secure and stable network, we were featured once again as one of the most active projects on Github. We are slashing PR wither related to the layer1 blockchain, the API endpoints, or blobbers challenges.
Let’s give a big shout-out to the dev team and all their effort!
As premmainnet events approach, we would like to get the Active Set (AS) to be more involved. If you are part of the AS, make sure to post questions on Telegram, or send them directly to me (Tiago) or Chad!
Last week, the blockchain and blobber team worked together to address the blobbers challenges pass rate issue. Meanwhile, they finished most of the code review for the token bridge smart contract and autorizers servers. This week, the team will be fixing the remaining issues that were found and reviewing the code for 0swap to address any potential security issues.
Blockchain Team Updates
Last week the Blockchain team mainly closed 18 PRs and 7 issues:
The blockchain team fixed:
1) a chain stuck issue that was caused by a mistakenly hidden ‘node not found’ error.
2) a security-related issue on fixed a security-related issue on zcnsc mint smart contract that it would pass the signature verification if there is no signature provided. With security in mind, we want to provide the best possible experience for our users and community.
3) a security-related issue on zcnsc, where it did not check if the client id was the target client id that is validated by authorizers. This fix will prevent malicious users from performing man-in-the-middle to mint tokens for themselves.
4) a bug on blobber delegate pool update event
5) empty index for user event updating https://github.com/0chain/0chain/pull/1554
6) emit events on updating of blobber details.Terms.
More fixes were conducted for potential overflow math operations. Furthermore, the team replaced git patch with scripts to update blobber config for running conductor tests as part of integration tests, and removed duration flag using on conductor tests for zbox rp-lock, and removed the unused DataRead field from blobber storage node to make the data struct compact, and returned UsedAllocation field in blobber API response. Lastly, when updatingthe min lock config, a fix was added which prevents a value from being auto-assigned thus preventing potential errors.
Blobber & gosdk team
The blobber and gosdk team closed 13 PRs, mainly for addressing the blobbers challenges pass rate low issue.
The team fixed:
1) a hash_mismatch error, as well as the Refs ordering issue
2) the challenge CreatedAt timestamp ambiguity
3) challenge issues partially by:
- Adding lock between object path calculation and writemarker commit
- Fixing database connection leakage
- Using goroutines to send requests to validators
- Allowing blank allocation to be valid.
4) OOM by loading and processing challenges one by one
5) ref ordering issue on renaming
6) a concurrent map read access issue
Finally, they added SDK for swap functions and exposed APIs on wasm for swap wallet and token.
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.
