IOTA has taken another significant step in the evolution of its consensus technology after enabling Starfish-Speed on the network’s Devnet, marking the next stage in a rollout designed to improve validator efficiency while maintaining the security guarantees introduced by the Starfish consensus protocol.
The update follows the successful deployment of Starfish on the IOTA mainnet earlier this year and comes after developers merged Pull Request #12287 into the protocol’s development branch. The change, which is scheduled for the upcoming v1.28.0 release, enables the optimistic commit rule known as Starfish-Speed on the Devnet and represents another milestone in IOTA’s roadmap toward faster and more resilient consensus.
Starfish-Speed Builds on Starfish’s Security Improvements
Consensus protocols determine how blockchain validators agree on the order of transactions, even when some nodes experience delays, outages, or malicious behavior. Earlier this year, IOTA introduced Starfish to replace Mysticeti, focusing on improving network reliability under difficult operating conditions.
Starfish introduced several architectural improvements. Instead of transmitting full transaction data throughout the consensus process, validators exchange lightweight metadata while transaction data is reconstructed using Reed-Solomon erasure coding. The protocol also requires validators to contribute a block before participating in the next consensus round, reducing the likelihood of network stalls following disruptions.
Related: IOTA Community AMA: Price Outlook, TWIN Progress, Kraken Delisting, and What’s Next
These changes significantly improved worst-case confirmation performance. According to previously published performance figures, the protocol reduced p99 confirmation latency from roughly 486 milliseconds to approximately 312 milliseconds, meaning the slowest confirmations became considerably faster.
However, the increased resilience came with a trade-off. Median confirmation times and p90 latency increased slightly because of the additional validation steps required by the protocol. Starfish deliberately prioritized reliability over maximum speed.
Starfish-Speed is designed to address that trade-off by introducing an optimistic fast path for normal network conditions while automatically reverting to the more robust consensus path whenever network instability is detected. This approach is widely used in distributed computing systems to balance performance with fault tolerance.
Developer Commits Highlight Performance Optimizations
The GitHub repository also reveals another notable optimization merged alongside the Devnet activation. Developers reduced one timing parameter from 100 milliseconds to just 5 milliseconds following extensive testing involving 20 validators operating under geographically distributed network conditions.
Benchmark results showed relatively stable overall commit latency across different timing configurations. Median confirmation times remained between roughly 254 and 263 milliseconds, while p95 latency stayed near 740 to 745 milliseconds. Overall throughput also remained consistent at approximately 2,000 commits per second.
The more meaningful improvement appeared in validator participation rather than raw transaction speed. Validators with weaker network connectivity maintained nearly identical block production rates, averaging approximately 16.2 blocks per second across all participating nodes. This suggests the optimization could improve fairness and consistency among globally distributed validators, an important consideration for decentralized networks operating across different regions and internet infrastructures.
Related: IOTA Investors Split Over TWIN Strategy as Community Defends Token Utility
Notably, two of the developers behind the implementation are also authors of the original Starfish research paper, highlighting the direct translation of academic consensus research into production-ready blockchain software.
Although Starfish-Speed is now progressing through the Devnet stage, investors should recognize that this remains part of IOTA’s controlled release pipeline. The Devnet currently operates with a limited number of Foundation-controlled validators rather than a fully decentralized production environment, and many of the published performance figures come from simulations rather than public network operation.
Related: IOTA Needs a New Captain—Here’s Why
If IOTA follows its recent release cadence, Starfish-Speed could eventually progress through Testnet before reaching Mainnet after additional validation and testing. Another major protocol improvement, known as P-COOL, remains under active development but has not yet entered any public network phase.
While Starfish-Speed may not dramatically increase headline transaction throughput, its focus on maintaining strong validator participation, improving optimistic execution, and preserving the reliability gains of Starfish represents another incremental step in IOTA’s long-term strategy of building enterprise-grade blockchain infrastructure capable of supporting global-scale decentralized applications.
About The Author
