Enjin Blockchain "Fort Canning" Upgrade

By
Enjin
October 6, 2026
Developments
Ecosystem
Enjin Blockchain "Fort Canning" Upgrade

Lend your rarest sword to a friend for the weekend, knowing it comes back on Monday. Give every player a season pass that vanishes when the season ends. Lock a legendary item's edition number for good, so not even the studio that made it can change it.

From November 16, all of this is built into the Enjin Matrixchain, the network where Enjin's games, collections and marketplace run. Fort Canning is the largest upgrade to the Enjin Blockchain since launch. Along with new kinds of tokens, it makes marketplace listings and offers smoother and brings OpenGov to the Matrixchain. ENJ holders will propose and vote on its future directly, as they have on the Enjin Relaychain since the Kallang upgrade in May.

If you play, collect or hold ENJ, you don't need to do anything. Your ENJ, tokens, collections and listings carry over as they are, and the Enjin Blockchain keeps running through both upgrades.

At a glance

  • Enjin Relaychain: Monday, November 9, 2026, at block #18,059,100 (approx. 16:00 UTC).
  • Enjin Matrixchain: Monday, November 16, 2026, at block #12,331,000 (approx. 16:00 UTC).
  • Live on Enjin Canary since September 28 and 29, 2026.
  • Downtime: none. The Matrixchain marketplace pauses for up to 30 minutes on November 16.
  • Node operators: every Matrixchain node must run client v1.4.0 or later before November 16, and Relaychain validators must run client v1.8.0 before November 9. See What You Need to Do below.

OpenGov Comes to the Matrixchain

OpenGov is the same governance the Enjin Relaychain has run since Kallang:

  • Anyone can propose a change, on one of fifteen tracks suited to different kinds of decisions.
  • ENJ holders vote directly, and can add weight to their vote by locking their ENJ for longer.
  • The Enjin Fellowship can fast-track time-sensitive proposals, such as urgent fixes. ENJ holders still vote on them.

From November 16, changes to the Matrixchain, including its next upgrade, go through OpenGov. Read more about governance and staking on Enjin.

Fort Canning also tunes the governance parameters on both chains to better support fair, decentralized decision-making. Submitting a referendum takes a 1,000 ENJ deposit, refunded when it passes or is cancelled, and every track now needs a minimum level of support, measured against all ENJ in existence, before a referendum can pass. The full parameters are in the changelog.

New Tools for Games and Collectors

From November 16, every feature below works in Enjin Wallet, on NFT.io and through the Enjin Platform.

Token Lending

An owner can lend a non-fungible token to another account for a set period. The borrower can use it like any other token they hold, but cannot list, burn or transfer it. When the period ends, the token returns to the owner automatically. The owner can extend a loan but cannot take the token back early, so both sides know what to expect.

How games can use it:

  • Let new players try a premium character, weapon or mount for a few days before they decide to buy one.
  • Run tournaments with loaned gear, so every team plays with the same set and the items go back afterwards.
  • Let guilds equip new members from a shared collection, with items that return when the loan ends.

How collectors can use it:

  • Lend a rare item to a friend, or to a player who needs it for an event, without giving up ownership.
  • Put items that would otherwise sit in a wallet to use in games that reward holding them, and get them back on schedule.

Whoever mints a token decides whether it can be lent. Tokens created before the upgrade can be lent once their collection owner turns lending on. Lending is built for rentals, trials and in-game loans. It is not a financial product: there is no collateral and no interest.

Ephemeral Tokens

A token can be minted with an expiry date up to a year ahead. When it expires, the network destroys it automatically and releases its deposit.

How games can use it:

  • Season and battle passes that end with the season.
  • Time-limited boosts, event items and daily quest rewards that do not pile up in players' wallets.
  • Demo items for a free weekend.

How events and communities can use it:

  • Tickets and access passes that disappear after the event.
  • Badges and rewards for a single season, such as a Multiverse Quest season.

For collectors, items that have served their purpose simply disappear instead of cluttering a wallet.

Mint Rate Limits

Collection owners can cap how many units of a token, or of a whole collection, can be minted in a given period. Tightening a limit takes effect immediately. Loosening or removing one takes 72 hours, visible on-chain the whole time, and can be cancelled if something is wrong.

For studios, this limits the damage if a minting key is ever compromised or a bug mints too much. For players and collectors, it is a public commitment about how fast supply can grow, which anyone can check.

Frozen Attributes

Collection, token and token group attributes can be frozen permanently. A frozen attribute can never be changed or removed by anyone, including the collection owner.

A studio can freeze the attributes that should never change, such as an item's edition, origin or metadata link, and leave others, such as level or experience, free to change through play. Collectors can check on-chain that what they own will stay the way it is.

Marketplace Listings and Offers

Listings and offers on the marketplace are upgraded to be more streamlined and efficient:

  • When you list an item and someone has already offered your price, the sale completes in the same step.
  • Offers on items sold in quantity, such as crafting resources, can be partly accepted.
  • Expired listings and finished auctions settle on-chain on their own.
  • Existing listings, offers and bids carry over unchanged.

Counter-offers now work through the same listings and offers. A seller can answer an offer by listing the item at their own price, and a buyer can answer a listing with an offer at theirs. Counter-offers still open at the upgrade are refunded in full, so settle any you want honoured before November 16.

 

Developers can build with all of these features today on Enjin Canary, where both upgrades are already live.

Under the Hood

  • Fuel tanks, which let games pay transaction fees for their players, keep their creation deposit with the tank's creator and apply their rules more strictly.
  • Staking. Nomination pool rewards are paid per exposure page, so payouts keep working as pools grow. You can stake through nomination pools on NFT.io.
  • Polkadot SDK stable2606 on both chains, with new tools that let wallets estimate the fee of a cross-chain transfer before sending it.

Upgrade Day

Both chains keep producing blocks throughout.

  • November 9, Relaychain: transactions pause for a few blocks while storage migrates.
  • November 16, Matrixchain: transactions pause for a few blocks, and the marketplace pauses for up to 30 minutes while listings move to the new format. Transfers, minting, fuel tanks and everything else work as normal.

Earlier Matrixchain upgrades paused the whole chain for up to an hour. Fort Canning limits the pause to the marketplace.

What You Need to Do

Players and collectors (Enjin Wallet, NFT.io): settle any open counter-offers before November 16 and keep Enjin Wallet up to date. Nothing else is needed.

ENJ holders and stakers: nothing. Pool rewards continue automatically. You can vote on the Relaychain upgrade at gov.enjin.cloud.

Game studios on the Enjin Platform: nothing. You can try the new features on Enjin Canary now.

Node operators: every Matrixchain node must run client v1.4.0 or later before block #12,331,000 on November 16, or it stops following the chain. Collators need v1.4.1. Relaychain validators must upgrade to client v1.8.0 before November 9, and we recommend it for every other Relaychain node. Validators and collators also need a new ofcw session key. Guides: Upgrading a Relaychain node and Upgrading a Matrixchain node.

Wallets, SDKs, integrators and exchanges: both chains change their transaction version, and transactions signed with the old version are rejected after each upgrade. The technical notices are in the Fort Canning changelog.

Decided by Governance

Both upgrades go to a vote. The Relaychain referendum is planned for submission on October 12, with enactment fixed at block #18,059,100. The Matrixchain upgrade is approved through the Matrixchain's current governance process from November 10 to 13 and applied on November 16.

Both proposals are published in advance with their exact calls and code hashes, so anyone can check the on-chain referenda against them: GP-2026-10-12-01 (Relaychain) and GP-2026-11-10-01 (Matrixchain).
 

Versions: Relaychain runtime 1.8.0 (spec version 1080, transaction version 19). Matrixchain runtime 1.4.1 (spec version 1041, transaction version 14). The full list of changes is in the Fort Canning changelog.

 

Fort Canning Hill was the seat of Singapore’s 14th-century kings and later of its colonial government. Today it is a public park, open to everyone. It felt like the right name for the upgrade that brings OpenGov to the Enjin Matrixchain.

Stay in the loop

Be the first to know about ground breaking innovations in the Enjin Ecosystem.
Thank you! Your subscription has been received!
Something went wrong!

You'll receive:

  • News and announcements from the Enjin Ecosystem
  • Exclusive opportunities to win high-utility NFTs.
  • Invitations to special events and beta testing.
  • Early access to new features and tools.