Last week, our tech team wrapped up an important sprint, with two major tasks on Interactive Roadmap: (1) implementing metadata to support leases for pinned files and (2) deploying a new version of curium (running on Cosmos SDK 0.47) in our internal test network. Here’s a breakdown of what we aimed to achieve, the progress we made, and what’s next.
What Did We Aim to Achieve?
Our goals for the sprint were twofold:
Deploy the latest curium chain: We set out to run the latest version of curium in our internal test network using Cosmos SDK 0.47. This would allow us to resolve any network build issues so that we can proceed with testing, ultimately deploying the upgraded curium in our beta test network.
Implement metadata support for leases: We also planned to deploy the initial code that supports metadata for leases around each pinned file, allowing us to begin testing and further development in that area.
What Did We Achieve?
We successfully deployed the curium chain running on Cosmos SDK 0.47 in our internal alpha test network, though not yet in the beta test network. Before deploying into beta, we need to complete testing for the typescript-sdk and curium-cli, which are critical to ensuring everything runs smoothly.
However, our progress wasn’t without challenges. The new version of Cosmos SDK introduced several changes, and deprecated libraries caused issues that required extra steps to resolve. We also discovered and addressed pre-existing issues that became apparent with the upgrade. While setbacks like these are common in the software development lifecycle, they provide valuable insights for future work.
Unfortunately, we weren’t able to implement metadata supporting leases for pinned files in this sprint. A multi-validator testing issue forced both of our team members to focus on resolving that blocker.
What Did We Learn?
This sprint gave us important insights into the new Cosmos SDK version. We now have a better understanding of which dependencies are compatible with the upgrade and what causes errors. The unpredictability of these kinds of changes is a reminder of how difficult it can be to forecast timelines accurately in blockchain development.
One major achievement is that we’re now able to build networks of multiple validators with the upgraded curium—a significant milestone as we continue to scale our platform.
What’s Next?
In the coming weeks, we’ll focus on testing the typescript-sdk and curium-cli to ensure everything is ready for deployment into beta. Once that’s done, we’ll shift our focus back to the metadata support for leases, which we’ve promised to our community. We’ve updated the public roadmap.
We’re excited about what’s ahead and appreciate your patience as we continue building and testing.
See you in two weeks!