In my previous post, I covered the updates that have already appeared on @SeismicSys GitHub. Now I decided to take a closer look at what the developers are currently working on and which updates are still in progress. github.com/SeismicSystems October 23: additional protection for private transactions. A fix has been proposed for a bug that, under certain conditions, could cause a private operation to be treated as public. This could potentially expose hidden data. The fix has already been proposed but hasn't been merged into the main codebase yet. September 28 – October 12: further Google Cloud support. Developers are continuing to integrate Google TDX into the tools used to run the network. The goal is to make it possible to configure and verify Seismic's secure nodes not only on Azure but also on Google Cloud. Some of the necessary changes have already been implemented, but the integration is not yet complete. August: a new encryption key management system. A new mechanism is still in development, where special encryption keys will be issued under the supervision of a security council rather than generated automatically upon request. This will provide better control over access to the keys used to protect private data. October 9: improvements to developer tools. Fixes have been proposed for Python tools to help applications correctly select smart contract functions and process encrypted data. This should reduce errors when building financial applications on Seismic. October 21: an example of a private bidding application. A community member proposed an application where companies can submit bids without revealing their amounts. The winner is determined inside a secure environment, while other participants' data remains hidden. For now, this is a community-built example of what Seismic can do, not an announcement of an official product. Based on the open tasks on GitHub, the main focus right now is on protecting private data, managing encryption keys, improving network infrastructure, and making developer tools better for financial applications. Some of these changes are being developed by the team itself, while others are being proposed by the community. @crypto_kesha @xealistt @NoxxW3 @heathcliff_eth