Welcome to the next crypto level
← Nexorena

Technologie & IA

Polkadot Fellowship releases runtime version 2.6.0 for Polkadot and Kusama

The November 19 release contains changes for the relay chains and several specialized chains. On Collectives Polkadot, it shifts the calculation of certain time periods to relay-chain blocks.

Nexorena Editorial Team

Polkadot Fellowship releases runtime version 2.6.0 for Polkadot and Kusama

A different time reference for Collectives

The Polkadot Fellowship published version 2.6.0 of its runtimes on November 19, 2026. The November 18 changelog details changes to the programs that define the rules for several Polkadot and Kusama chains. All runtimes in the release move to stable2609-2 of the Polkadot SDK. The release provides access to the code and files for that version. It does not give an activation date for each chain.

On Collectives Polkadot, the modules governing promotion and demotion for Fellowship members and ambassadors use relay-chain blocks to measure time. They previously used Collectives blocks. The stated goal is to preserve the real-world length of these periods if the Collectives block interval changes. The migration converts the stored periods and timestamps. One 12-second Collectives block then counts as two relay-chain blocks.

Reorganized queues and elections

The Polkadot and Kusama relay chains gain a module to run migrations over multiple blocks. On those same chains, downward message queues move to paged storage. These messages travel from the relay chain to attached chains. The changes concern how runtime work and data are organized. The changelog gives no figures for any improvement in user throughput.

The code for both relay chains also removes the multi-phase election module and its associated on-chain election. The changelog says staking elections already take place on Asset Hub following its migration. A migration in this release clears the old module’s storage. On the Polkadot and Kusama Asset Hubs, signed election submissions now store the base deposit fixed at registration. A migration derives it for existing submissions.

Changes specific to specialized chains

On People Polkadot, the release caps the number of people with lite status at 10,000. It throttles paid lite registrations after a threshold is reached. A separate function lets a statement store slot holder move the slot to a different account at most once every 15 minutes. Person records also retain a history of their recognition in the system.

The release therefore describes rules specific to each chain and migrations that vary according to the data it holds. The common version number identifies a set of software published by the Fellowship. Establishing when these rules take effect on a chain requires evidence of activation on that chain. The changelog accompanying the release does not provide that evidence.

Article sources

Written with love byEthan BrooksMeet this editorial pen name ↗

Explorer Nexorena