Züs Weekly Debrief — December 07, 2022
Happy Wednesday! I hope everyone is doing well. Tomorrow we will have our Cloud Cover AMA (Ecclesia 4) on Thu December 08 at 10 am PST, so make sure to attend! Last week on Ecclesia 3, Saswata revealed the demo for our wallet App Bolt He explained how to create a wallet, staking, and delegating. In addition, Sculptex successfully conducted onboarding tests with the Active Set as preparation for Pre-mainnet.
Blockchain Team Updates
Last week the blockchain team mainly focused on a few known smart contract issues and closing the transaction fee PRs. Meanwhile, the group continued working on the staking fix PR and testing it with the front-end team. Moreover, several trivial issues were detected and fixed, including a panic issue on the snapshot. Beyond these changes on the 0chain repo, they worked on our SDK on the gosdk repo to support our front-end teams. Check for more details below:
The team fixed a security issue on the challenge verification smart contract. The main problem was that the **verifyChallenge** function did not adequately verify the validity of the validation tickets, allowing for potential forgery. Additionally, waiting to load data from MPT for reward is recommended until the challenge verification is completed to avoid wasting resources. For more details about this, check issue 1838.
Also, a sharder panic issue was fixed on loading snapshots. This was mainly caused by checking the wrong event type round number. The events are being processed in round order so that the snapshot can be initialized on round 1 and saved to the database. The snapshot would be loaded from the database for any event with a round number greater than 1. Even though this is correct, one type of event could be triggered and processed out of round order, resulting in a panic if they were triggered before the snapshot was initialized.
Settings were added to the event database that mirror global settings in the blockchain. Null fields were fixed on APIs, especially on WriteMarker/ReadMarker related endpoints and removed unnecessary fields from the transaction response. Also, the team fixed a sharder fault tolerance test and an API for an empty blobber_id on the read marker response.
Furthermore, a new valid origin was added for all prod web apps and a new function that takes a file name and returns more details about the file. This includes the blobber information on gosdk. They removed client_id from wzcn. Mint allowed the zcnbridge client to specify a wallet, added the ‘burnZCN’ method on wasm, the zboxapi SDK, and exposed it on windows/android/ios/wasm SDKs. Finally, they fixed a panicking issue on PlaylistConsensus and revealed jwt methods on winsdk and fixed the RefreshJwtToken issue.
I hope you all enjoyed the update!
Züs is in the news!
Economy Middle East spoke with Saswata Basu, Züs CEO and founder on how, The FTX fiasco could reshape crypto forever — Economy Middle East.
Read our most recent articles:
Blockchain-based Storage Solutions are likely to become the norm.
Transformative power of blockchain: The ways businesses benefit.
Developer Resources
- Interested in learning more about building on Züs or becoming a service provider? Check out our GitHub for access to repositories. Community ambassador Sculptex has created numerous tutorials to help get you started.
- Try our BetaNet here! Users can create wallets and allocations, store files, send transactions, and share files.
- Need help navigating creating wallets, allocations, or joining as a blobber? Check out our documentation page.
- Züs’s API endpoints use simple and intuitive HTTP requests to interact with the blockchain in order to send/retrieve information to and from miners, sharders or blobbers in the active network.
About Züs
Züs (formerly 0Chain) is a high performance storage network powering limitless applications. It is a new way to earn a passive income from storage.
