Enjin marked NFT.io's scheduled maintenance complete at 16:06 UTC on November 16, closing a marketplace interruption that began at 15:40 UTC. The status notice described the work as a marketplace storage migration. For users returning to the service, that is a concrete completion signal, but it should not be stretched into confirmation that every Enjin service or upgrade feature is available.

The distinction matters because Enjin's status page also carries a separate token-migration incident. A completed marketplace maintenance window does not resolve that other entry. Users need to check the service involved in their particular action, rather than treat one green status as a network-wide clearance.

The marketplace window has closed

The maintenance entry was posted at 13:17 UTC on November 16, ahead of the work. Its start and completion timestamps put the recorded interruption at 26 minutes. That duration describes the status record; it is not an independently measured account of every user's experience.

For someone with a marketplace action in progress, the useful next step is to establish what happened to that action. A refreshed page alone does not establish whether a prior transaction was included. Keep the transaction reference and check its outcome before signing a replacement.

Fort Canning provides the upgrade context

Enjin's Fort Canning changelog had warned of a marketplace interruption around the Matrixchain upgrade scheduled for November 16. It identified Matrixchain runtime v1.4.3 and distinguished that work from the earlier Relaychain upgrade. The published plan and the maintenance completion are related operational records, but they answer different questions.

The changelog also gives a specific instruction to exchange operators handling withdrawals: check whether a transaction was included before re-signing it. Withdrawals rejected across the upgrade boundary may need the new signing versions. A rejected signature and a completed withdrawal are not interchangeable outcomes.

That is the practical importance of a runtime upgrade for a service connecting to a blockchain. An operator can have a working interface while a transaction prepared under earlier assumptions needs attention. The appropriate check concerns the actual transaction and its signing context, not just whether the website loads.

New capabilities still need their own checks

Enjin's upgrade explanation describes NFT lending that lets a borrower use an asset for a defined period while restricting transfers, listing and burning. It also describes expiring tokens and changes to collection settings. These are project-described capabilities, not evidence that every collection has enabled them or that a particular lending market is active.

Collection settings matter. Enjin says lending must be enabled by the collection owner. A reader should therefore inspect the terms of the specific asset and application before assuming that an upgrade announcement gives an existing NFT new rights.

Our crypto wallet guide explains why control of signing keys and the behavior of an application are separate responsibilities. The transaction fee guide provides background for checking a new submission's cost.

Read completion at the right level

The fresh development is the completed NFT.io maintenance window. Confirmation of a particular runtime's enactment, a collection's configuration or a user's pending action requires its own record. Keeping those checks separate lets users resume work without either dismissing a completed maintenance job or claiming more from it than Enjin's notice establishes.