Happy Wednesday! This week, we have a plethora of dev updates on both the blockchain and decentralized storage sides as the team continues to round out API feeds, improve documentation for easing adoption, and prepare for long-term network scaling. Thank you again to everyone who has already signed up for our decentralized storage application, secure wallet, or storage provider platform. If you have not already, make sure to take advantage of our extended deadlines to earn rewards.
Development Team Updates
The blockchain and smart contract teams have merged 18 PRs and closed 15 issues over the past week. Building upon prior weeks’ testing and debugging, the team has implemented various fixes to address performance and API feeds. The team identified bugs and implemented fixes for the /getUsersPool API endpoint, which would cause the incorrect return of the client’s pool info, as well as the /alloc-written-size-per-period endpoint.
New APIs were implemented to provide the amount of data added during a range of blocks, provide support to searching by block range for the getTransactionByFilter, and to return transaction hashes when filtered by LookUpHash, Name, or ContentHash. The team’s rigorous testing ensures that API feeds provide accurate information while maintaining security. This is important so that front-end applications and users can securely access information. In turn, the team has also removed unnecessary swagger documentation to prevent redundancies.
Outside of addressing API-related issues, several updates were made for key network functionality and event database scalability. With the team’s recent testing, they were able to identify and fix an issue within conductor testing which would cause the creation of rounds too fast, resulting in the tests failing as the rounds would exceed the desired stopping point. Database-related fixes include improving the process of updating allocations to prevent a new need for a new allocation as well as bugs related to the validator-related interactions with the event database.
Memory Leak Issue Fix
A memory leak issue was detected that could cause the crashing of sharders. A fix was implemented to limit the event channel buffer size from 1 million to 100. Key generation scripts were updated to include the -tag bn256 build tag in order to ensure it performs adequately. Block reward constants were moved to the sc.yaml and MPT. These constants, which were previously hardcoded, are used for calculating block rewards. Thus must perform as anticipated in order to ensure service providers are properly rewarded. The team also updated the magic block generation in order to meet mainnet requirements.
Sharder may upgrade and tier their decentralized storage
The blockchain team has also been working on the ability for sharder’s to upgrade and tier their storage. This is critical for future-proofing the sharders’ decentralized blockchain storage. As the network scales and time passes, sharders will be tasked with storing block history which will build up. By allowing sharders to store data on multiplied devices or even tiering them onto network storage for older, infrequently accessed blocks, the team is preparing for ensuring high network performance and long-term success of network scalability.
The Blobber and gosdk team have closed 9 PRs in the Blobber and gosdk repos in the past week. The team updated the code to support file listing, which providers support for specifying a file path instead of a directory. This update makes the process work similarly to the Linux ls command, which should return a file. In collaboration with the blockchain team’s fixes on conductor testing, the Blobber team also fixed a compilation error for conductor tests.
Following testing and review of the znft sdk, the team implemented suggested fixes for the NFT-based functionality. The team added further support for $ZCN price feeds on the blobber side to ensure accuracy when creating allocations or staking. Additional focus on mobile support for zcncore functionality. The team added support for TransactionSchema and iOS frameworks/simulators. They also finished its PR for gomobile SDK build so that all the SDK could be supported for mobile development.
Züs is a high-performance storage platform that powers limitless applications. It’s a new way to earn passive income from storage.