As we wrap up another productive two weeks ending December 6, 2024, we’re excited to share the progress we’ve made on our ongoing upgrades to Curium, the Cosmos SDK, and Curium-CLI. These upgrades are critical to enhancing our platform’s functionality and stability, and while challenges remain, we’ve made significant strides forward.
What Did We Aim to Achieve?
This sprint, our focus was on two key goals:
- Upgrade Curium, the Cosmos SDK, and Curium-CLI.
- Upgrade the SDK governance (gov) module and deploy it to the testnet
What Did We Achieve?
While there’s still work to do, we’ve achieved several milestones, including resolving major issues and unlocking new functionality:
Curium-CLI Compilation Errors Resolved:
We successfully fixed compilation errors for the Curium-CLI upgrade. This was a crucial step in ensuring the tool functions seamlessly with the updated modules.
Curium-CLI Tests Fixed Across Modules:
Test issues were resolved in various modules, including: authz, bank, distribution, keys, mint, nft, staking, status transfer.
Most modules are now functioning correctly, with only the params and gov modules requiring further attention.
Governance Module Upgraded:
The Cosmos SDK governance (gov) module was successfully upgraded from v1beta1 to v1, marking a significant enhancement in governance functionality.
Params Module Issue Fixed:
The long-standing issue with the params module was resolved, allowing us to move closer to a complete deployment.
What’s Next?
Here’s our plan moving forward:
- Review Module Changes:
Conduct a thorough review of the changes made to the params and gov modules in both Curium and the Cosmos SDK to ensure alignment and functionality.
2. Prepare for the Next Software Upgrade:
Set up comprehensive tests to validate the next software upgrade on the testnet. This will help identify and resolve potential issues before deployment.
3. Integrate the Auth Module:
Add the auth module into the SDK and complete the implementation of the updated governance module, incorporating the new functionality provided by the auth module.
Final Thoughts
Upgrading core components like Curium and the Cosmos SDK is always a challenging process, but the progress we’ve made in this sprint reflects the dedication and expertise of our team. As we move closer to deploying these upgrades into the testnet and beyond, we’re excited about the increased capabilities and robustness these changes will bring to the Bluzelle ecosystem.
And keep on top of the latest with our public roadmap: https://trello.com/b/vqwJLgvz/bluzelle-public-roadmap
