Welcome to the next crypto level
← Nexorena

Altcoins

Enjin activates the Fort Canning upgrade on its Relaychain

Enjin’s Relaychain activated Fort Canning on November 9. The network’s public node shows the specification version changing from 1070 to 1080 around the scheduled block 18,059,100. The Matrixchain upgrade has a separate vote and schedule.

Nexorena Editorial Team

Enjin activates the Fort Canning upgrade on its Relaychain

The version change is visible at the following block

Relaychain referendum 16 approved the upgrade on October 28, according to Enjin’s changelog. The change was due to be applied at block 18,059,100. The official node returned specification version 1070 at that block, followed by 1080 at block 18,059,101. The network had already finalized block 18,059,106 when checked. Enjin calls the Fort Canning runtime version 1.8.0.

Enjin asks Relaychain operators to use client 1.8.1. This version of the software that runs the node includes upstream security fixes. It does not change the version number of the chain’s runtime upgrade. The distinction matters to operators and integrators. An up-to-date client number and the specification version observed on the network describe two different things.

Governance settings and transaction signing change

Fort Canning adjusts deposits and support thresholds used in Relaychain governance. Enjin says the new values also apply to referendums already in progress at activation. Its changelog also lists changes to pool payouts and to accounts that sponsor fees for some transactions. The changes affect how the network operates beyond the vote that approved the upgrade.

The Relaychain transaction version moves from 18 to 19. According to Enjin, transactions signed with the previous version are rejected after activation, including transactions signed in advance or still pending. Clients that read the version and metadata before each signature can pick up the new values. Offline signing tools and integrations that hard-code the values must update them. Enjin says balances and the address format stay the same.

The Matrixchain stays on a separate schedule

The Matrixchain is due to receive a different version, 1.4.1. Enjin puts its referendum on November 10–13 and targets November 16 for implementation if the proposal passes. Activation on the Relaychain does not establish that the Matrixchain has upgraded. Operators working on both chains need to check their software and network versions separately.

The Matrixchain schedule includes a marketplace interruption of up to 30 minutes, while the other functions Enjin describes would continue to operate. That window concerns the second upgrade. For the Relaychain, the evidence available on November 9 is the version change confirmed by the public node, with blocks finalized beyond the scheduled point.

Article sources

Written with love byEthan BrooksMeet this editorial pen name ↗

Explorer Nexorena