protocols
Enjin schedules the Matrixchain Fort Canning upgrade for November 16
Enjin’s schedule targets 16:00 UTC for the Matrixchain rollout. The upgrade is set to bring OpenGov, migrate marketplace listings, and change the transaction version.

The schedule targets block 12,319,600
The second stage of Fort Canning covers Matrixchain, the Enjin network that hosts its games, collections, and marketplace. After the November 9 Relaychain upgrade, Enjin’s technical changelog schedules the new Matrixchain software for Monday, November 16, around block 12,319,600 and 16:00 UTC. These are estimates. The actual block depends on when the authorized upgrade is applied.
The listed Matrixchain runtime is version 1.4.3, moving the specification version from 1031 to 1043. Enjin distinguishes the runtime applied onchain from the client each operator installs to follow the chain. The announced minimum client version for nodes is 1.4.1. Version 1.4.3 is recommended because it contains upstream security fixes.
A short migration for marketplace listings
Enjin expects the chain to keep producing blocks, with user transactions pausing for a few blocks during migration. The marketplace is expected to stay unavailable for up to 30 minutes from the enactment block. Listings, offers, and bids are meant to carry over. Open counteroffers follow a separate rule: they are removed and refunded in full under the published migration schedule.
The upgrade also adds functions for gaming and collectible tokens, including lending and the creation of tokens with a limited lifetime. It brings OpenGov to Matrixchain, where ENJ holders will be able to propose changes and vote. Future network upgrades will use that governance process. Enjin says funding requests will go to the Relaychain treasury and spending from the Matrixchain community pool will be suspended.
Transaction handling changes for integrators
The Matrixchain transaction version changes from 12 to 16. Technical instructions say transactions signed with an older version will be rejected after enactment, including some transactions prepared in advance. Tools that bundle fixed settings or metadata need to account for the new values. Enjin says balances, deposit addresses, and the address format stay the same.
For exchanges and custodians, Enjin recommends pausing deposits and withdrawals from 15:30 UTC. Resumption depends on two checks: the node must report specification version 1043 at a finalized block, and a test transaction signed with version 16 must then be finalized. The pause applies to operations that rely on a node. Its actual duration will depend on enactment and the outcome of those checks.
