Mainnet and App updates:
Happy Wednesday! We hope you’re doing well as we approach some major milestones with the Mainnet rollout and the release of our demo apps. We are excited to share that the Mainnet development is progressing rapidly, with several issues already resolved and merged. While we had planned to release the App demos this week, we have decided to take some extra time to ensure that everything is perfect. Therefore, we will be postponing the release by at least one week. We believe that this decision will ensure that we can deliver the best possible experience for our users. We will keep you updated on any further developments and appreciate your continued support.
Storm of the Week:
Data Localization Trend
Today I came across an article from Forbes: “Privacy In A Borderless World: How To Navigate The Data Localization Trend And Protect Your Organization”. The article emphasizes the importance of companies prioritizing privacy protection and their compliance with local data regulations to avoid legal and reputational risks. To ensure transparency, accountability, and security in data handling practices. The author suggests the implementation of a data governance framework for ensuring transparency, accountability, and security in data handling practices. For more information on this, please refer to the article.
As a result of regulatory discrepancies across different countries, data localization is becoming a growing trend in the business space, making moving data a liability for businesses.
In a borderless world where the demand for protecting privacy is increasing tremendously, organizations can reduce the risk of non-compliance with local data regulations by selecting where their data is stored with Decentralized Storage. Decentralized storage not only enhances data security and transparency but also enables users to control their own data and monitor access to it. With the Züs Network, users are able to select service providers based on their geo-location to distribute their data according to their own jurisdictions. Meanwhile, it generates an immutable record on the blockchain. In this way, companies can avoid regulatory risks and comply with privacy regulations, like GDPR.
Big Tech accelerates AI adoption
Both Google and Microsoft are rapidly adopting AI in their products to enhance productivity and streamline workflows. Google has recently added new AI features to its productivity suite, including grammar suggestions, smart compose, and assisted data visualization in Docs, Gmail, Slides, and Sheets. Microsoft has also been incorporating AI into its products, such as Excel, PowerPoint, and Word, with features like Ideas and Presenter Coach.
As AI technology continues to advance, we can expect to see more innovative features from both tech giants and others in the industry, as they seek to provide the best possible user experience and stay competitive in the market. The fast adoption of AI in big tech is driving the development of these features, which will ultimately benefit users in terms of increased productivity, efficiency, and accuracy in their work.
Moreover, the surge in demand for AI-driven solutions is also driving data consumption to unprecedented levels. This presents an opportunity for Decentralized Solutions like Züs to shine, by offering more sustainable, efficient, private and scalable alternatives to meet the exponential demand.
Blockchain Team Update:
TXN fee test errors:
Last week the team continued sorting out the txn fee system test errors. Most errors have been fixed. However, some test cases behaved weirdly. Some test cases failed because the team asserted that txn will have a cost, even if they fail. The weird part is that the tests failed when runned all together, but not when manually on each case.This makes the debug process longer than usual, as it takes at least 1.5 hours to run all the test cases to reproduce the error.
A few assumptions were made and tested:
First, the balance checking API might have a bug related to the event db, so we changed it to access MPT directly, but it didn’t make any difference. The second assumption is that the txn fee was not set when the client submitted the txn; unless the txn cost value is 0, the txn could not pass the validation. So, it’s not related, either. The team will add logs to check a third assumption that the txn fee payment transaction didn’t go through successfully. We will see the result shortly.
Chain Stuck Issue:
The blockchain team checked the logs for the stuck issue on the large network. They pointed out in the logs that the last partition item was removed right before detecting the last partition item could not be found. The bug might be found there, which will be investigated after the txn fee system test issues are resolved.
Beyond these issues, the blockchain team merged the following core PRs:
The team filtered validators according to LastHealthCheck, added smart contracts to kill/shutdown blobber and validator, refactored global snapshot calculation, and added unit tests for provider aggregate calculation + global snapshot updates.
Furthermore, the team merged the cancel_allocation SC optimization PR, added `validator_health_check` cost in sc.yaml to unlock the system test errors, and added script to generate migration files, prefixed with current unix timestamp at UTC+00 with goose migration boilerplate. Also, they added health check logic for authorizers and updated “mint” smart contracts, and fixed a distributing algorithm of rewards for the authorizers—reward only one authorizer each on each `mint` SC.
In addition, the team checked if a blobber/validator existed on the chain before they were sent to the add_blobber/add_validator transaction, fixed filepath.Dir and path.IsAbs issue on Windows, fixed a `has no entry in fileID meta` bug on `createdir` and `newfile` commands, and exposed “lockStakePool”, “unlockStakePool,” and “getstakePoolInfo”.
Also, the blockchain team fixed download shared encrypted file issue in wasm, fixed verify with public key issue on wasm, fixed the `has no entry in fileID meta` bug on `createdir` and `upload` commands, fixed renameworker.go to handle errors arriving from go routine, and fixed decodeAuthTicket returns `undefined` on wasm.
Furthermore, the team added methods to retrieve from sharders the last processed mint nonce and a list of not processed burn tickets for a certain ethereum address. This change adds WASM methods, which are used to get a list of not, and processed burn ZCN transaction hashes and not processed burn WZCN transaction hashes. Also, it ads a zcnbridge method, which is used to get a list of not processed burn ZCN transaction hashes, and ads support of “SubgraphURLAPI” param in bridge.yaml, which is used to establish a connection with “The Graph” GraphQL server.