Welcome to the next crypto level
← Nexorena

Technologie & IA

IOTA releases a preview of protocol 40 for its test network

The 1.36.1-rc preview sets epoch 724 as the earliest possible activation window. It also changes how nodes index data and how applications look up history.

Nexorena Editorial Team

IOTA releases a preview of protocol 40 for its test network

An upgrade threshold on Testnet

IOTA's maintainers released version 1.36.1-rc on November 11 for the public test network. It introduces protocol 40 and says it can be activated no earlier than 19:24 UTC, at the start of epoch 724. An epoch is a period during which the network operates with a given set of validators. Releasing the software and opening the activation window are separate steps. The release notes do not provide a network record showing that the upgrade threshold was reached.

The notice primarily addresses validator operators. If the threshold is met, a validator still running an incompatible version is removed from the committee, depriving that validator and its delegators of test network rewards. IOTA's documentation says test tokens have no real-world value and are specific to the network on which they were obtained. The preview describes an environment-by-environment rollout and sets no activation timetable for protocol 40 on the main network.

An index rebuilt at first startup

The update combines the former JSON-RPC and gRPC indexes in a common database. Full nodes rebuild the index when they first start after the upgrade. Startup waits for the live object scan, and transaction and event history then fills in in the background. That process can use only checkpoints the node still holds. A service responding to queries therefore does not establish that the index has already caught up across the full period of retained history.

The release also changes historical storage. Older object versions are grouped by epoch, allowing whole periods to be removed as they leave the retention window. The maintainers say the first startup can refuse to migrate if disk space is insufficient. How long to retain data thus becomes an operational choice that determines both the amount of data kept and how far back the node can answer queries.

Cursors become opaque values

For applications, the change shows up in paginated responses. Several JSON-RPC methods now return opaque cursors. Instead of reconstructing a cursor from an object ID or transaction digest, a client must use the value returned by the preceding response. The old JSON-RPC server's WebSocket subscriptions are also removed. Applications combining pagination and live monitoring need to test those two uses separately when trying the preview.

The release also updates the fee calculation model and introduces new limits on the size of values passed to Move calls. A validator attestation mechanism appears behind a dedicated setting. The notes describe its activation on Devnet, while leaving it disabled on Testnet and the main network in this rollout. Testnet can therefore be used to check the planned changes for nodes and clients while keeping the scope of each experiment distinct.

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena