Active Set Update | Züs Weekly Debrief September 20, 2023
Today’s Active Set Update:
The Active Set (AS) members are diligently testing Chimney, Atlus, Blimp, and Vult on the AS network. We are grateful for the invaluable feedback on bug detections and UI/UX improvements. Our upcoming phase involves redeploying the network for the conclusive tests, which are anticipated to begin within the next week.
We are excited to extend an invitation to our entire community to participate in testing our Apps on the AS network. Your invaluable feedback will expedite our progress and aid in identifying any lingering issues.
Join us in refining our products. Your insights are crucial to our advancement!
Storm of the Week:
The Rise of S3-Compatible Storage Solutions
In today’s digital age, secure and efficient storage is crucial. While Amazon’s S3 has been a top choice for cloud storage, the demand for more flexible and cost-effective alternatives is growing.
What does S3-compatible storage bring to the table?
Flexibility: Organizations can choose storage solutions that best meet their specific needs while still maintaining the familiarity and functionality of the S3 API.
Cost Savings: Competitive pricing without the surprise of hidden fees.
Easy Switch: Transitioning to an S3-compatible solution from Amazon S3 is hassle-free.
Recognizing this evolution, we developed Blimp. It is more than just storage; Blimp embodies our forward-thinking vision, delivering a combination of higher uptime, swift recovery, and security protection. Our commitment? An impressive 99.99% data uptime and unparalleled data recovery standards.
Curious about how Blimp stands out? Delve into our latest exploration of the Top 7 S3-Compatible Storage Solutions.
Blockchain Update:
Last week, the blockchain team completed the Live Test for both DEX and NFTs, finalized the bluetooth implementation for zauth desktop and iOS bolt, and addressed the video transcode issue in Vult web upon uploading. Additionally, a resolution was found for the sharder issue that arose during block syncing. However, the team is currently addressing another sharder panic issue linked to slow event DB writing and challenges in restarting after prolonged operation. Efforts to resolve these two concerns are ongoing. Concurrently, the team will focus on video streaming on the Web end.
Below are the detailed updates:
A discrepancy was noticed in the DEX contract during the Live Test. The ZCN token listed at address 0xb9EF770B6A5e12E45983C5D80545258aA38F3B78 lacked the increaseAllowance() contract function. Instead, increaseApproval() needs to be invoked. The contract was deployed without the increaseAllowance() function. Upon correction, all DEX contracts performed as expected.
The tests revealed that NFT contracts operated efficiently. The issues encountered were due to incorrect configuration of the ethereum_node_rpc address, which erroneously pointed to the Mumbai contract addresses. Corrections ensured smooth operations.
For zauth and bolt iOS, the Bluetooth implementation was finalized. Key accomplishments include:
- Correction of package assembling in both zauth and iOS ends. The team added 2 bytes to the data beginning to indicate its size, facilitating receiver processing.
- Integration of subscriptions for setup characteristic and transaction characteristic, necessary for iOS bolt responses.
- Completion of split key setup and transaction signing, complemented by the above bluetooth refinements.
The sharder encountered synchronization challenges due to divergent notarized blocks for identical rounds. The solution involved syncing the block to the in-memory block store post state computation. This issue was resolved in PR #2771.
The video transcoding issue in the Web end was addressed by upgrading ffmpeg.wasm to 0.12.6 from 0.10.0. The solution involved lazy loading, delaying ffmpeg package imports until video upload initiation.
Additionally, several PRs and issues were closed. Details are as follows:
- PR #2771 — Sharder sync issue during block synchronization
- PR #2775 — Workflow modifications for conductor
- PR #2741 — Challenges based on rounds
- PR #2777 — Issue regarding challenge ordering was addressed.
- PR #2778 — An unlock allocation concern was fixed.
- PR #2782 — Checks were instituted to ensure minimum mint amounts aren’t less than the maximum fee.
- PR #2780 — A challenge was fixed.
- PR #2785 — WP unlock issue was addressed.
- PR #2787 — An authorizer conductor test problem was fixed.
- PR #1221 — A path removal problem was resolved.
- PR #1220 — Path header was removed.
- PR #1225 — Send function in wasm was exposed.
- PR #1226 — A directory renaming error was corrected.
- PR #1249 — A limit increase was implemented for open challenges per fetching.
- PR #1239 — Commits were refactored.
- PR #1250 — An error encountered during directory renaming was fixed.
- PR #1251 — A blobber replacement issue was addressed.
- PR #1225 — Asynchronous processing was introduced.
- PR #1254 — Block download limits were adjusted.
Stayed tuned for another Active Set Update
Ultimately, we are committed to ensuring that the Active Set system is operating efficiently and securely for all users while also working to streamline the user experience. We understand this requires the dedication of our resources as well as collaboration and feedback from our community members in order to continue pushing the limits of innovation. As always, we value your patience and trust in us as you join us on this journey. So do not forget to follow us on our various social media channels to stay updated as much as possible about future Active Set updates! We would not have been able to make it this far without you, so again, thank you for being part of this incredible journey with us. Stay tuned for another Active Set update soon!
