Empowering the Future: OzoneChain Governance Forum https://coinlayers.com/empowering-the-future-ozonechain-governance-forum/

LYDRA Performance Patch Update (0.20.17) I hope this message finds you all well. As previously mentioned, I'm reaching out today to share some important updates and reflections on the recent LYDRA 2/2 patch (0.20.16) Firstly, let's address the elephant in the room: the resource issues some nodes encountered. It's clear now that our LYDRA implementation, despite its ingenuity, had some performance issues with some nodes. This complexity stems from the fact that our EVM layer doesn't directly track HYDRA balances. We bridge this gap using the Account Abstraction Layer (AAL) that comes from the hybrid UTXO/EVM model – essentially an adapter that translates and records events between the UTXO and EVM layer. To break it down, fetching a single direct representation of HYDRA balance on a wallet isn't straightforward due to the underlying complexity of the UTXO protocol. UTXOs are balances on their own, and to get the total balance, one must fetch all UTXOs separately. Nodes need to first gather all present UTXOs using "getaddressutxos" call, and then sum these values as a subsequent operation. This sum helps determine the total HYDRA balance, and whether the minted LYDRA exceeds that balance, which in turn dictates the spendable amount for a wallet. This process, though necessary, demands extensive read/write operations, putting a strain on our nodes, especially those with limited resources. Post-deployment, we observed that nodes with lower resources were significantly impacted, experiencing CPU spikes and slow syncing. To address this, we recommend using nodes with NVME hard drives. However, we've noticed that cloud instances deployed from older snapshots (pre NVME cloud instances) may not fully leverage the latest NVME performance due to outdated kernel files and drivers. If your cloud instance was deployed from an old snapshot and falls into this category, we strongly advise planning a fresh deployment on a new instance. We've already released version 0.20.17, which significantly improves performance and comes as a critical update (doesn't require any activation, just straightforward install). This update has been tested across various nodes, showing improvements of up to 1000% compared to version 0.20.16. This is a big win for us, as it dramatically streamlines the validation processes critical for HYDRA transfers and make post LYDRA mainnet much more feasible in terms of scalability and performance. Without a doubt, the LYDRA launch was one of the most technically challenging tasks we've ever done and I also want to congratulate the community and the team for the hard work and patience. Comparatively, in Ethereum-compatible chains, these operations are replaced by a single call to fetch a wallet's balance – a simplicity we're aiming to take full advantage with HydraGon. Speaking of HydraGon, I'm thrilled to share that our progress is on track, with the public testnet scheduled for January 2024 (aiming for first half of Jan). Our goal is to have 90% of the functionality available on the testnet, and I'm excited to report that LYDRA is already fully operational on HydraGon. In closing, I want to extend my heartfelt thanks to all of you in the Hydra community for your unwavering support. Your loyalty and patience have been the backbone of our journey. Wishing everyone an amazing holiday season and I looking forward to an exciting new year with HydraGon! Make sure to patch your node in the meantime -> https://github.com/Hydra-Chain/node/releases/tag/hydra_v0.20.17