Dec 14
Züs Weekly Debrief — December 14, 2022
Happy Wednesday! Last week our Cloud Cover (Ecclesia #4) was postponed due to connectivity issues. We apologize for the inconvenience. However, we will be hosting the AMA tomorrow (Thursday, December 15th at 9 am PST). In the past few days, the Active Set has been performing multiple onboarding tests in preparation for the magic block generation process, which will launch the pre-mainnet network. Make sure to attend the AMA to hear more about the status of the pre-mainnet onboarding of the Active Set. Now let’s dive into this week’s update!
Bolt
In our last AMA (Ecclesia #3), Saswata unveiled our revolutionary Bolt app and gave an incredible demonstration of its capabilities. The Bolt app is a non-custodial wallet that gives you safety and complete control over your ZCN. The Bolt app will allow you to buy and sell ZCN to ETH, support credit cards, and stake your tokens. Bolt users will have the opportunity to easily invest in the storage business. With staking, users will be able to delegate their tokens to servers (blobbers) to earn based on their actual demand for storage. Not only does Bolt Staking provide a direct path for investment in the storage business, but it is also transparent and measurable on the blockchain. Züs Storage-based Defi provides a real and tangible income by giving users the ability for unlimited earning potential.
In addition, the app uses our Split-key 2fa security technology which provides serverless two-factor authentication that does not rely on vulnerable and centralized servers. The protocol splits your keys into two or more devices to protect your funds with the same security as a hardware wallet but has the convenience of choosing your own devices to approve transactions. Rest assured, even if one device is compromised you can still restore your wallet with your mnemonic key, just like a hardware wallet.
Blockchain team updates
Last week the blockchain team focused on fixing the transaction fee issues and spent some time debugging the system test errors of the challenge verification smart contract PR. They also located and fixed a bug that caused the chain to move slowly and sometimes caused a round timeout on the small network. The issue only happened in the small network when chaos tests were turned on, and only happened in extreme circumstances. After the fixes, the chain moved smoothly and barely got a round restart. Also, the team finished the staking fix PR and merged all related PRs. Check below for more details and other key fixes:
Fixed the slow chain issue on the small network (3 miners) with chaos and load tests.
The chain would get stuck for a while till the round timeout occurred. This happened when one of the block generators was down and the running generator got a ‘node not found’ error. The team did a quick node states syncing for block verification before, but it was not done for the block generation process. So, when getting an invalid state error on generating blocks, it will be necessary to wait for the round to restart to re-generate the block. The fix was simply performing a quick state syncing and retry just like for the block verification.
Transaction fees
- Implemented transaction fee estimate based on cost logic, updated the API for getting estimated transaction fee and implemented the transaction fee validation on the transaction submit API handler and on the transaction process logic.
- Updated gosdk to support transaction fees. Implemented the logic to send requests to miners to get an estimated txn fee as the minimal fee before sending a transaction. The functions are all done, but systems tests will need to be adjusted due to the requirement of txn fee, which will be addressed in the following week.
Other fixes
- Fixed staking to support frontend Apps, a VRF tickets cache related slow consensus issue, and a panic issue on an unknown provider. When an unknown provider is sent in response, a nil stake pool can be returned.
- Also, fixed issue that restarting a node would re-enter the genesis block generating code. The genesis block should never be re-run the genesis block generating’ code once the chain has started. The state should be deterministic and only changed by new transactions.
- Added missing configs and initial staking support on the genesis block. This is for initializing the stake when starting the chain for the active set providers. Removed overwriting transaction_id, added new data aggregates to the database, and implemented conductor tests that lock the network till all nodes are registered in fault tolerance tests.
- Furthermore, made some redis adjustments on connection parameters as the miner failed to connect, added zcnbridge function to get nonce, and fixed setWallet issue on wasm before SDK initialization. Also, fixed zcnbridge burnZCN on wasm and a nil allocation check to prevent panic on mobile SDK.
Züs is in the news!
Read our most recent articles:
A decentralized storage economy: crypto market to the next level (zus.network)
Data breaches are on the rise — but decentralized storage can help (zus.network)
Developer Resources
- Build for the future - Sign up for our SDK
- 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.
