SIX-MONTH TECHNICAL UPDATEOver the past six months, the Bluzelle engineering team has executed a wide array of deep infrastructural and protocol-level improvements to the Curium blockchain, its surrounding deployment tooling, developer SDKs, and CI infrastructure. These changes span multiple subsystems, reflecting our ongoing commitment to operational robustness, ecosystem compatibility (notably with Cosmos IBC), and modern software development standards.

✅Core Blockchain & SDK Upgrades

• Upgraded Curium and Cosmos-SDK Core:
  • The core Curium blockchain has been upgraded to Cosmos-SDK v0.47.15, resolving multiple compatibility issues and specifically unblocking the IBC relayer bridge to Osmosis, which had previously been hindered by upstream changes. This upgrade was non-trivial and involved comprehensive updates across Curium’s transaction processing, governance, and query logic.
• Storage Module Overhaul with Go-IPFS Integration:
  • A full upgrade of the chain’s storage module was conducted in conjunction with the update of the go-ipfs dependency to its latest release. Due to the move to Go 1.22, multiple dependency paths were restructured and recompiled to ensure ABI compatibility and runtime correctness. This significantly improves IPFS-backed file storage reliability and compliance with future upstream changes.
• SDK & CLI Alignment:
  • The TypeScript SDK (typescript-sdk) and the Curium CLI (curium-cli) were both fully refactored to align functionally and semantically with the upgraded Curium protocol. All public-facing commands, flags, and argument structures were reviewed and updated for consistency, including enhanced helper text and improved command documentation for developers.

⚙Deployment, Infrastructure & Automation Enhancements

• Rewrite of Deployment Scripts:
  • All deployment tooling has been overhauled to support seamless provisioning of new nodes, new full networks, remote testnets, and explorers, with full support for both SSL and non-SSL deployments. The scripts now support dynamic image selection, Dockerfile-based binary building, and local-to-remote deployment transitions.
• Expanded CI/CD Coverage:
  • New Jenkins jobs and CI tasks were added to automatically deploy and verify:
    • New validator and sentry nodes (client, gateway, and sandbox roles)
    • Snapshot-based state sync tests
    • End-to-end software upgrade flows, including transaction submission tests
    • No-faucet branch behavior, ensuring faucet endpoints are correctly disabled
• Automated TCP Port and Content Verification:
  • Post-deployment verification now includes TCP port checkers to confirm open ports on all services, and content checkers to validate that explorers and RPC endpoints return the expected chain data and status information.
• Infrastructure Code Refactors:
  • Improved usage of logDir and NVMe mount points for optimal I/O performance
  • Corrected Docker network configurations in remote network scenarios
  • Modularized SSL key and certificate handling across all components
  • Refactored reverse proxy handling to dynamically configure NGINX/Traefik per swarm
• Snapshot Synchronization Enhancements:
  • Infrastructure tooling now includes waiters for snapshot readiness to ensure downstream services (like validators joining mid-network) can sync state via State Sync without human intervention. This is especially crucial for ephemeral deployments and devnet testing.
• Resilient Re-Image Capability:
  • Re-imaging logic was refactored to support clean Curium binary rebuilds from updated Dockerfiles. This includes accurate re-creation of image layers to eliminate stale state artifacts in rebuilds.

🔧System & Environment Modernization

• Mainnet Stability Restored After AWS Maintenance:
  • All halted nodes were successfully restored following AWS maintenance interruptions. Node persistence strategies have been improved to mitigate future impact from scheduled EC2 reboots.
• Tooling & Runtime Upgrades Across the Stack:
  • Node.js upgraded to v22.16.0
  • Jenkins upgraded to v2.513
  • TypeScript and Lerna versions upgraded in the mono-repo for better compatibility with newer language features and package management patterns

📦Post-Fork Swarm Simulation and Explorer Resilience

• Post-fork configurations can now be used to bring up local swarms to simulate mainnet upgrade paths.
• Explorers have been adapted to deploy under both SSL and non-SSL conditions, with network modes configurable at runtime, ensuring testnet mirrors and mainnet portals are more robust.

This update reflects a significant evolution in the resilience, automation, developer tooling, and ecosystem alignment of the Bluzelle Curium blockchain. Every change is aimed at preparing the chain for continued growth, seamless developer onboarding, and interchain interoperability.Next Steps

• Final robustness testing is underway across testnets that accurately mirror mainnet conditions.
• Each testnet is upgraded from v9 to v10, then from v10 to v11, replicating the actual lifecycle of the mainnet.