Happy Wednesday! Thanks to everyone who participated in our referral campaign for the storage app, which ended on this Monday. In the last week, the dev team mainly focused on newly encountered bugs that caused the chain to be stuck and worked on optimizing the load tests. Meanwhile, they fixed several issues on blobber and gosdk that were exposed by load tests. Let’s dive into this week’s update!
The blockchain team worked on two different tasks. One for supporting the development of the Apps, and fixing bugs, and optimizing load tests. Since a lot of effort was needed for fixing the chain stuck bug and load tests, not many PRs were closed, as they still need to be reviewed. Therefore, only 4 PRs were closed in the 0Chain repo while 9 new PRs are currently being reviewed.
The team fixed the chain stuck issue by the ‘state hash mismatch’ error. For this, they went through the smart contracts packages of minersc, storagesc, zncsc, faucetsc, and related common packages to locate all the places that could have this error. They fixed all of the places where the APIs should return but didn’t. Also, they fixed incorrect async block and round storing (when finalizing blocks), which now should be saved to db synchronously instead. In addition, they fixed potential goroutine leaks. All of these issues were addressed to improve network stability and ensure that the network features will be highly performant upon launch.
Moreover, they fixed an issue with the timestamp of write markers and transactions, which could produce the same time stamp, which previously was treated as an error. Also, they enhanced the open challenges API endpoint by querying with more accurate time ranges, updated /collected_rewards to support start and end-date as query parameters, and added a special parameter called data points to specify the number of data points in the output.
Blobber & gosdk team
The Blobber & gosdk team closed 11 PRs in the blobber and gosdk repos
The team fixed:
1) the open challenge pass rate low issue, improving the challenge methodology to work more efficiently.
2) a blobber dir delete issue caused by LIKE statement.
3) a root path renaming issue, the root path / dir should not be allowed to be named.
4) a foreign key constraint error while deleting related commit_meta_txns.
5) a signature verification issue on wasm.
6) a renaming issue that was detected during load tests.
In addition, they merged the code in blobber repo to support listing recent add refs, which will be used by clients to list recently added files. They merged the mobile SDK into staging. Lastly, they exposed createDir API on wasm.
Züs is a high-performance storage platform that powers limitless applications. It’s a new way to earn passive income from storage.