The release of IOTA’s v1.21.1 marks a significant architectural shift for the network, introducing the Starfish consensus mechanism to mainnet alongside a series of deep protocol and infrastructure changes. While version updates are often treated as incremental, this upgrade carries structural implications that extend across consensus, networking, indexing, and node operation layers. The activation of Starfish is paired with a move to protocol version 24, signaling a coordinated modernization of the network stack. In parallel, legacy components are being deprecated or fully removed, indicating a deliberate tightening of the system’s core design.
What makes this release notable is not just the addition of features, but the removal and consolidation of older architectural paths. The deprecation of REST APIs, migration of gRPC toward TLS-secured communication, and restructuring of indexer behavior all point toward a more unified and secure infrastructure model. These changes also introduce operational requirements for node operators, particularly around migrations and service restarts. As a result, v1.21.1 is less an upgrade and more a coordinated redefinition of how IOTA nodes interact across the ecosystem.
Related: IOTA Positioned for Growth as EU–South Korea Trade Pact Advances Digital Infrastructure
Starfish Consensus and Protocol v24 Upgrades
The most important change in v1.21.1 is the activation of Starfish consensus on mainnet, marking a shift in how agreement is achieved across the network. This upgrade also introduces protocol version 24, aligning system-level logic with the new consensus design. Starfish is deployed across all networks in this release, ensuring consistency between test and production environments. This unification reduces fragmentation and improves predictability in validator behavior.
Alongside the consensus upgrade, several foundational dependencies have been updated to support long-term scalability. RocksDB has been upgraded to version 0.24.0, improving storage performance and stability under high throughput conditions. The AuthContext has also been extended with tx_data_bytes and signing_digest fields, adding more granular transaction representation. Additionally, the signing Intent structure has been integrated into the IOTA framework to improve execution clarity.
Related: IOTA Powers Healthcare Transformation in Argentina With Vitalnode Project
Node-level observability has also been refined in this release, particularly for validators and full nodes. Authority gRPC metrics have been renamed for consistency, including inflight_grpc becoming authority_grpc_inflight_requests. Similar standardization applies to grpc_requests and grpc_request_latency metrics. These changes improve clarity in monitoring systems and reduce ambiguity in performance tracking.
Together, these updates indicate a deliberate move toward a more structured and observable protocol layer. By aligning consensus, storage, and metrics under a unified versioned framework, IOTA is reducing operational fragmentation. This also sets the foundation for more predictable validator behavior under Starfish. The result is a tighter coupling between protocol logic and node execution.
Infrastructure Hardening: gRPC TLS, REST Removal, and Indexer Overhaul
One of the most operationally significant changes in this release is the introduction of TLS for gRPC connections between nodes and validators. This strengthens communication security by encrypting validator interactions at the transport layer. At the same time, CLI updates ensure that node operators now rely on secure gRPC channels by default. This change reflects a broader shift toward eliminating unsecured or legacy communication paths.
In contrast, the REST API has been fully removed in this release, marking a decisive end to its role in the IOTA node stack. Any systems relying on REST-based checkpoint sourcing for indexers must now be reconfigured to use gRPC exclusively. This transition introduces operational overhead, particularly for legacy deployments, but consolidates all data flows into a single transport mechanism. Operators should expect migration and restart requirements as part of this change.
The indexer subsystem has also undergone significant restructuring in v1.21.1, particularly in how data changes are tracked and processed. Unwrapped objects are now included in transaction object changes, and JSON-RPC endpoints return encoded object bytes when available. A new backfill command allows operators to populate historical object-change data. These enhancements improve completeness and accuracy in indexed data.
Related: IOTA Backs Turing Certs in Building Digital Identity Infrastructure for Real-World Governance
Pruning and dependency management have also been redesigned to improve resilience and performance. The pruning system now operates on per-table watermarks, allowing independent retention policies across database tables. Optimistic indexing has been updated to use object-based dependency checks, making it more robust against pruning of older transactions. Additionally, RPC reads now detect when queried data has been pruned and return appropriate errors.
Operational changes introduce new migration requirements that must be carefully managed by node operators. A database migration removing the redundant objects_owner index is expected to take at least 60 minutes during restart. The IndexerExecutor workflow has also been updated, replacing run() with run_with_config() and shifting default behavior to CheckpointReaderV2. These changes also include breaking adjustments to remote store URL handling, requiring updated configuration formats.
Related: Clawnera Builds AI Bot Economy on IOTA for Machine-to-Machine Work
Further updates extend into the API and developer-facing layers of the system. JSON-RPC responses now include unwrapped objects within objectChanges, improving transparency in transaction outputs. GraphQL introduces a new effectiveCommissionRate field for validators, aligning with IIP8 specifications. Before protocol version 20, this value defaults to the standard commissionRate. CLI updates remove deprecated commands such as iota start and genesis workflows, further streamlining the toolchain.
Taken together, v1.21.1 represents a consolidation phase for IOTA’s infrastructure, removing legacy systems while reinforcing core protocol and networking layers. The shift away from REST, the tightening of gRPC security, and the deep restructuring of indexing logic all point toward a more unified architecture. At the same time, the introduction of Starfish consensus and protocol v24 marks a foundational evolution in how the network reaches agreement. This release ultimately signals a transition from modular legacy systems toward a more integrated and security-focused protocol design.
