Technologie & IA
IOTA releases a protocol 41 alpha for its development network
Version 1.37.0-alpha introduces dependencies between programmable transactions outside mainnet and the public testnet. The release notes set November 21 at 18:29 UTC as the earliest possible activation on the development network.

Possible activation at epoch 29
On November 20, 2026, the IOTA project released version 1.37.0-alpha of its node software. It introduces protocol version 41. On the development network, or devnet, that version can activate no earlier than November 21 at 18:29 UTC, when epoch 29 begins. That is the earliest activation time. The notes do not say that the upgrade threshold has already been reached.
The project asks devnet validators to update their nodes before the epoch changes. If the threshold is reached, a validator that has not upgraded can be removed from the committee, with a loss of rewards for it and its delegators. The warning concerns the development network. The release notes do not give an equivalent schedule for activating transaction dependencies on mainnet or the public testnet.
A transaction tied to a previous outcome
One protocol change lets a programmable transaction name an earlier transaction it depends on. The second can run its commands only if the first succeeded during the same epoch. According to the release notes, protocol 41 enables this mechanism on networks other than mainnet and the public testnet.
The rule matters when an application needs to run two operations in sequence. If the first fails after the second has been ordered, the second also fails. Its commands do not run and failed-transaction fees apply. The notes distinguish this case from one in which the node does not yet know the prerequisite transaction. An application testing the feature therefore needs to distinguish an unknown dependency from a prerequisite already recorded as a failure.
Node changes to test as well
The prerelease also changes how validators handle incoming transactions. The authors describe a counting change that includes a transaction as soon as it is admitted to the relevant control mechanism. The aim is to keep the consensus queue within its configured limit when multiple transactions arrive together. The notes also say that validators no longer lose certain transactions accepted just after an epoch change.
The upgrade imposes a compatibility requirement for local databases. A node will refuse to start if its database was last written by a version older than the 1.36 series. The project says to start it with a 1.36 release first in that case. Feedback from testing can help assess the behavior of linked transactions and the effect of the upgrade on development installations.
