Deep Dive
1. Starfish Consensus & v1.6.1 Release (10 September 2025)
Overview: This mainnet release introduced an experimental implementation of the Starfish consensus protocol. It's designed to improve the network's ability to keep progressing even if some nodes experience delays, aiming for greater resilience.
The key change separates block header propagation from block data dissemination. In simple terms, this allows slower nodes to catch up in the background without holding up the entire network's agreement process. It's currently marked as experimental and not enabled on any live networks, undergoing internal testing before a potential future testnet deployment. The release also included adjustments to the Indexer backfill tool and added IOTA-Names commands to the CLI.
What this means: This is bullish for IOTA because it lays the groundwork for a more robust and reliable network, which is critical for handling high-value enterprise and institutional applications. A network that doesn't stall under pressure builds greater trust with developers and users.
(Source)
2. IOTA Wallet v1.3.0 Update (3 September 2025)
Overview: This was a maintenance update for the official wallet, focusing on refining the user experience and updating underlying software libraries.
The changes included fixing a form for managing NFTs to prevent display issues, updating documentation links, and upgrading the software development kit (SDK) it depends on. These are typical incremental improvements that keep the wallet running smoothly and securely.
What this means: This is neutral for IOTA as it represents ongoing, essential maintenance rather than a major new feature. It ensures the core user interface remains stable and secure, which is fundamental for everyday holders and users of the network.
(Source)
3. Mainnet v1.5.0 Performance & RPC Upgrades (27 August 2025)
Overview: This earlier major release delivered several backend improvements aimed at network operators and developers, enhancing overall efficiency.
For node operators, it added data pruning tools to save storage and a congestion tracker to monitor network traffic. For developers using the JSON-RPC interface, it introduced a new field to suggest optimal gas prices for transactions, making dApp interaction more efficient. It also improved the CLI with better JSON output options for checking validator information.
What this means: This is bullish for IOTA because it directly improves the experience for validators and builders. More efficient nodes and better developer tools lower the barrier to creating and running applications on IOTA, which is essential for long-term ecosystem growth.
(Source)
Conclusion
IOTA's recent codebase evolution shows a clear focus on strengthening network fundamentals—through experimental consensus research and practical node optimizations—while maintaining core user tools. This balanced approach aims to build a more resilient infrastructure capable of supporting its ambitious real-world trade and identity use cases. With the experimental Starfish consensus now in the codebase, how quickly will it move from testing to a live network deployment?