The primary keyword for this update is Enjin Kallang upgrade. Enjin's Kallang release puts Relaychain governance, staking, marketplace, and Polkadot SDK changes into the May 18 mainnet window, giving protocol researchers a chain-ops item to track.
For Radar, the owner-fit angle is not exchange routing. It is what changes inside the protocol stack and how operators should monitor the upgrade once the runtime goes live.
What Happened
Enjin lists the Kallang upgrade for Enjin Mainnet on May 18, 2026 at block 15,543,000, approximately 16:20 UTC, with runtime version 1.7.0. The post says the upgrade applies to the Enjin Relaychain, while the Matrixchain release notes are expected later.
The project describes governance improvements, staking fixes, and infrastructure updates. Items include removal of the legacy sudo pallet, dedicated sENJ conviction voting, nomination pool fixes, marketplace and multi-token pallet changes, and a Polkadot SDK update.
Why It Matters
The Radar reason to care is protocol operations. Removing sudo changes the emergency-control model, a dedicated governance pallet changes how staked ENJ participates, and nomination-pool cleanup can affect staking reliability. These are chain design signals, not just token market notes.
The marketplace and multi-token changes add another discovery layer. Permissionless cancel paths, partial fills, and token event changes can influence how builders and users experience the chain after activation, even if the headline upgrade is mostly infrastructure.
This is also why the same event can have a separate CryptoSigy article. Radar tracks runtime behavior, governance surface, and operator readiness; CryptoSigy tracks exchange transfer routes and execution risk.
What To Watch Next
Watch whether the target block activates cleanly, whether validators and infrastructure providers report issues, and whether post-upgrade governance actions use the new flow without friction. Also watch for the later Matrixchain notes, because Enjin says that follow-up is expected separately.
For dapp and ecosystem discovery, the useful follow-up is whether marketplace, token event, and governance changes show up in real user or developer workflows after the upgrade.
Continue this cluster
Continue this cluster with chain-upgrade and protocol-operations updates from the same discovery lane.
