Züs App demos | Cloud Cover AMA:
Happy Wednesday! Tomorrow we will be hosting our Cloud Cover AMA (Ecclesia #12), so make sure to attend on Thursday, March 30, at 9 am PST, as Saswata will be giving an update on Züs Mainnet and the Züs App demos! Make sure to add questions on the Discord channel for Saswata to answer or send directly to me on Telegram. Now let’s dive into this week’s update!
Storm of the Week:
AI development continues at full speed, so I will continue giving updates on its development, as we believe it will significantly impact data consumption and decentralized storage adoption. I hope you enjoy it!
OpenAI plugins
OpenAI recently announced the release of several plugins that allow users to customize and extend the functionality of their language model conversations. These plugins offer the ability to add new capabilities to the language model, integrate with other applications or services, and handle specific tasks. You can check out some of the plugins here.
Some examples:
- Browser Plugin: Allows users to have conversations with ChatGPT directly from their browser.
- Retrieval Plugin: Provides the ability to retrieve information from external sources and incorporate it into the conversation.
- Code Interpreter Plugin: Allows users to input and execute code during a conversation with ChatGPT.
Security Concerns
However, there are also security concerns related to conversational data with AI. OpenAI recently experienced a data breach where the titles of conversations and payment information were leaked to other users. This event highlights the potential privacy risks associated with centralized services and conversational chats.
In addition to OpenAI, other companies are also developing AI-focused tools. For example, Microsoft recently released a Security Copilot to help identify and fix security vulnerabilities in software code. While this tool is designed to work with human developers to provide suggestions and recommendations based on written code, there are concerns about the potential for it to be used for malicious purposes, such as creating more sophisticated malware or automating attacks. As AI continues to grow, companies will need a privacy solution for their storage, such as the Züs Network, which provides absolute privacy, data ownership, and higher security. We are working on a storage platform that can support the storage needs of AI while ensuring customers have complete privacy, control over their data and performance.
Blockchain Updates:
Last week, the blockchain continued fixing the txn fee system tests. The team fixed the strange behavior where some test cases failed on system tests run from github actions. The main issue was that the config of `max_fee` in github actions was not configured correctly. All the txns run even after the 0 as txn fee, leading to the system tests’ balance assertion failures. The team fixed this issue by adding the `max_fee` config to the 0chain/actions repo and by update set the estimate txn fee based on the cost with coeff when max_fee is 0; otherwise, the max_fee will be used if the calculated fee is greater than it.
Moreover, the team detected a miner/sharder register issue while fixing the system tests. When the first attempt failed, the miner/sharder failed to retry the register txns, which will attempt all the miner/sharder stake pool processes then. Check the fix in [Fix SetupSC mine/sharder register issue].
Also, the blockchain team fixed the validator health check txn issue; they all failed to send the health check txns because the validator health checks txn cost was misconfigured; see the fix in [Correct validator_health_check cost].
System Tests
Apart from the fixes in 0chain repo, most of the work was on system tests. Due to the bug mentioned above, most of the test cases were checked based on 0 txn fee, so multiple cases still need to be resolved. There are mainly three kinds of fixing: one is to add the `pour` command before running the test cases so that the zbox commands could have enough balance to pay the txns. The second is to extend the time for running tests. The third one is to adjust the balance assertion code. Most of the remaining cases we need to fix are the third kind and a few timeout cases. But the timeout cases could not be fixed easily by extending the time, so further investigation is needed in this part.
Beyond the txn fee fixes, the team fixed and raised several PRs:
The team implemented script + chacha20poly1305 for wallet encryption, and fixed upload and download cost calculation, fixed an that error occurs while downloading thumbnail for encrypted file, and a filepath issue on –remotepath. filepath.Join/filepath.Split/filepath.Dir are replaced with pathutil package.
In addition, the team added endpoints to kill and shutdown providers, an option for zwallet to get active authorizers only, a miner health check worker back, and they set up swagger for blobber.
Also, the team removed min lock and interestpoolsc settings and upgraded mcl & bls and all related repos in gosdk, zwallet, zbox, system tests. Both are approved and Ready to be merged after checking the system tests.
Additionally, the dev team fixed random map accessing in SCs, and added storage_token_stake to snapshort. Both are approved and ready to be merged. The team added endpoints to kill and shutdown provider, an option for zwallet to get active authorizers only, a miner health check worker back, and they setup swagger for blobber,
The team also removed min lock and interestpoolsc settings and upgraded mcl & bls and all related repos in gosdk, zwallet, zbox, system tests. Both are approved and Ready to be merged after checking the system tests. The dev team fixed random map accessing in SCs, and added storage_token_stake to snapshort. Both approved and ready to be merged.
