IOTA Mainnet Activates Starfish Consensus in Protocol v24 Upgrade

• Advertisement -

• IOTA has activated Starfish consensus on Mainnet through the v1.21.1 release and protocol version 24.

• The upgrade moves IOTA beyond its earlier Mysticeti setup and brings a new BFT consensus design into live production.

IOTA has pushed Starfish onto Mainnet. Not testnet, not a research note, not another roadmap sentence. Live.

The IOTA Mainnet just got a major consensus upgrade.
Starfish is now live. pic.twitter.com/Ri1kXeLVCx

— IOTA (@iota) April 28, 2026

The change arrived through IOTA v1.21.1, which introduces protocol version 24 and switches consensus to Starfish across the network. The IOTA explorer is now showing protocol version 24 with v1.21.1 active, a small line of technical text that carries rather more weight than it first appears.

For a chain that has spent years trying to turn research-heavy architecture into something usable in the open market, this is one of those upgrades that actually matters. Quietly, but materially.

Starfish Leaves the Testing Tank

Starfish had been moving through IOTA’s development pipeline for months. Earlier in April, the IOTA Foundation described the Q1 rollout as a successful deployment of Starfish consensus to testnet, positioning it as part of the network’s broader protocol evolution. That was the safe phase.

Mainnet is the point where the engineering has to survive ordinary network messiness, validator behaviour, infrastructure delays and the occasional ugly edge case that never quite shows up in a clean environment.

At its core, Starfish is a Byzantine Fault Tolerant consensus protocol built around a DAG-based architecture. IOTA’s own documentation describes it as optimized for low latency and high throughput, with an emphasis on keeping consensus reliable even when some nodes are faulty or malicious. That is the marketing-friendly version. The more practical version is simpler: the network is trying to make finality faster and sturdier without turning communication between validators into a bottleneck.

That distinction matters because IOTA has been leaning harder into real-world infrastructure use cases, especially trade, supply chain and digital identity. These are not areas where “works most of the time” is good enough. If a ledger is meant to support documentation flows between institutions, ports, agencies or commercial platforms, the consensus layer cannot behave like a science experiment every time conditions get rough.

A Technical Upgrade With Commercial Pressure Behind It

The timing is also interesting. IOTA’s Q1 update tied protocol work to trade infrastructure, including TWIN-related activity in the UK and Kenya. The Foundation has been trying to place IOTA less as a retail crypto story and more as infrastructure for regulated, paperwork-heavy environments. That is a harder pitch, but also a more serious one. Starfish fits neatly into that narrative because consensus reliability is not a side feature there. It is the product’s nervous system.

For token holders, the immediate question will probably be price. It always is. But the cleaner read is technical first. Protocol version 24 signals that IOTA is still actively rebuilding its base layer after the broader Rebased transition, and this upgrade gives developers and validators a new operating model to work with. Whether that turns into adoption is a separate question, and a more uncomfortable one.

There is also a reputational angle. IOTA has carried the burden of its own history for years, sometimes fairly, sometimes less so. Mainnet upgrades like this are how that story changes, if it changes at all. Not through slogans. Through code that runs, validators that stay online, and infrastructure that does not blink when conditions are less than ideal.

Starfish is now in that arena.