Deep Dive
1. Active Development Momentum (July 2026)
Overview: While there hasn't been a new versioned release since December 2025, the development team has been actively merging code improvements. This steady stream of updates suggests ongoing maintenance and feature preparation behind the scenes.
The GitHub pulse data shows 26 pull requests were successfully merged between 30 June and 6 July 2026, contributed by 3 developers. This level of activity in a single week points to a healthy, collaborative development cycle focused on refining the existing codebase.
What this means: This is neutral to bullish for IKA because it shows the project is not stagnant. Consistent code commits reduce technical debt and pave the way for future, user-facing upgrades, even if they aren't announced yet. A live project with active developers is more likely to adapt and improve over time.
(Pulse · dwallet-labs/ika)
2. Mainnet Protocol v3 Upgrade (2 December 2025)
Overview: This was a significant mainnet release that upgraded the core Ika protocol to version 3. For users, this update broadly expanded the types of blockchains and digital assets that dWallets can natively control without using bridges.
The key technical improvement was upgrading the network's encryption key to version 2, which added support for newer, more secure dWallet technology. This enabled support for additional signature algorithms like EdDSA (used by Solana and Cardano) and Taproot (Bitcoin), meaning one dWallet can now securely manage assets across a much wider array of networks.
What this means: This is bullish for IKA because it directly increases the protocol's utility and potential user base. By supporting more blockchains natively, it makes Ika's cross-chain technology more versatile and attractive to developers building multi-chain applications, which could drive more network usage and demand for the IKA token.
(Releases · dwallet-labs/ika)
3. Testnet Protocol v2 Preparation (17 November 2025)
Overview: This testnet release served as a foundational update, upgrading the protocol to version 2 and introducing enhanced cryptographic capabilities for the network's signer nodes. It was a critical step in testing the features that would later reach mainnet.
The update focused on the "Nodes & CLI" components, implementing support for a more advanced version of the two-party computation (2PC-MPC) system. This included improvements for generating signatures more predictably and efficiently, and added early support for the new curves and algorithms that were fully enabled in the subsequent v1.1.8 mainnet release.
What this means: This was a neutral, technical step for IKA. It demonstrated the team's disciplined approach to development by rigorously testing major upgrades on testnet first, which is a best practice for ensuring mainnet stability and security before releasing features to all users.
(Releases · dwallet-labs/ika)
Conclusion
Ika's development trajectory is characterized by a major, utility-expanding protocol upgrade followed by sustained codebase maintenance. The project balances significant technical leaps with consistent refinement. Will the recent flurry of pull requests culminate in another substantive protocol version soon?