Dusk Network ITNv2 Progress Update.

17 Feb 2024, 21:46

Dusk Network ITNv2 Progress Update We've confirmed the accuracy of the issue's initial description and are pleased to report significant progress. Following an upgrade to our cluster's specifications, the network has begun to self-repair and is progressively returning to a synchronized state. However, to ensure the network fully stabilizes, some nodes may require manual resynchronization. Below are the steps to manually resync your node: 1. Unstake your funds by running rusk-wallet unstake in your droplet's console. 2. Stop the Rusk service with service rusk stop. 3. Remove the chain DB and cache by executing the following commands: rm -rf /opt/dusk/rusk/chain.db/ rm -rf /opt/dusk/rusk/state/ rm -rf ~/.dusk/rusk-wallet/cache* 4. Restart the Rusk service using service rusk start. 5. Sync your node. You can monitor the last block height accepted by checking /var/log/rusk.log with the command tail -n 1 /var/log/rusk.log | grep "block accepted". The current block height is available on the [explorer](https://explorer.dusk.network/). 6. Restake your funds once close to the current block height, with rusk-wallet stake x, where x is the amount you wish to stake. In parallel, our team has been producing already a solution to the fallback procedure issue and adapted the rolling finality configuration to the faster block time. We're also enhancing the block repropagation logic for improved efficiency. These improvements will culminate in a binary upgrade, which we will schedule and announce in the coming days. Furthermore, the Discord-based faucet is currently undergoing final tests and will soon be released along with a detailed guide to ensure a smooth user experience. We are committed to maintaining transparency throughout this process and will continue to share updates as they become available. Your understanding and cooperation is greatly appreciated as we work together towards a more robust and efficient network.