Polkadot’s proposed Join-Accumulate Machine (JAM) is moving beyond research papers and broad technical plans. In September 2026, Polkadot developers released a production roadmap that provides a clearer timeline for JAM’s launch and explains how responsibilities currently handled by the Relay Chain will be reduced and migrated to a JAM-based service for finality. Finality, in this context, refers to the point at which confirmed results become irreversible.

The change would be more than a routine network upgrade for Polkadot. The current Relay Chain manages security, consensus and other coordination functions among Polkadot’s parachains. JAM is designed to replace that architecture with a more general-purpose distributed computing environment in which different services can run on shared infrastructure.

JAM remains under development, but the central question has shifted from whether it will be built to how Polkadot can migrate to it safely.

What JAM Would Change

Polkadot founder Gavin Wood introduced the JAM concept in 2024. The design seeks to remove many of the hardcoded limitations of the current Relay Chain and create a more general system capable of supporting a broader range of computational services. Wood’s original concept is described in Polkadot’s JAM explainer.

The Relay Chain is currently Polkadot’s primary coordinating layer. Validators maintain network security, parachains connect through the shared infrastructure, and the Relay Chain handles critical consensus and communication functions.

Under the new roadmap, many of those structures would change. JAM is being developed as production-grade infrastructure, while the existing Relay Chain would be phased out gradually. During the transition, its primary role would be to validate parachain execution.

The proposal therefore represents a structural redesign rather than an incremental performance upgrade.

Why the September Roadmap Matters

The September roadmap is significant because developers have begun addressing the practical engineering requirements for production deployment.

The PolkaJAM project is intended to become a complete JAM node implementation based on the Gray Paper specification, the formal document that defines the protocol’s rules. Before it can support production workloads, the software must be able to withstand attacks from malicious peers, denial-of-service attacks, network overload and unscheduled network shutdowns.

Developers are also building an in-browser light-node library that would allow applications to access JAM directly without relying on a separate light node to verify network information. In parallel, they are developing a new parachain service that would eventually bring parachain finality to JAM.

These projects focus on operational infrastructure rather than theoretical design. They are intended to provide the software, access tools and network services required for JAM to function in a production environment.

Why Polkadot Wants to Replace the Relay Chain

The existing Relay Chain was designed around Polkadot’s original parachain model. That model provided common security and interoperability, but it also established specific rules for how computation would be organized across the network.

JAM is intended to be more general. Instead of focusing primarily on parachains, it could allow different computational services to share Polkadot’s security and processing capabilities. Developers would be able to deploy services without necessarily seeking governance approval for every new type of execution.

The architecture is also designed to process work in a more parallel manner. JAM would shift Polkadot’s emphasis from a network of blockchains organized around a single dominant chain toward a distributed computing system in which network resources could support a wider range of applications.

How JAM Relates to Polkadot’s Broader Changes

JAM follows several changes to Polkadot’s technical and economic models. One of them is Agile Coretime, which replaced the previous parachain auction system. Under that system, projects had to collateralize a significant amount of DOT to secure a fixed, multiyear slot.

Agile Coretime makes the acquisition of network resources more flexible. Polkadot blockspace can now be viewed as a resource similar to computing power that can be rented according to demand.

Polkadot is also changing DOT’s economic model. Binance Insights noted that Polkadot would introduce a hard cap of 2.1 billion DOT in 2026, while annual issuance was expected to decline by approximately 53.6%.

The supply redesign is one of the largest tokenomic changes in Polkadot’s history. The previous model allowed continuous inflation. JAM is therefore part of a broader effort to rebuild both the technology supporting Polkadot and the economics underpinning DOT.

Whether JAM Changes DOT’s Role

JAM could affect how DOT is used, although the outcome will depend on the network’s evolving economic model. DOT currently has important functions in staking and governance, while access to network resources is connected to Polkadot’s coretime model, under which blockspace is rented as needed rather than secured through long-term slots.

As JAM reorganizes shared computing resources, the commercial role of DOT and demand for shared computing power could become more significant. The central issue is whether greater technical flexibility leads to increased demand for Polkadot’s infrastructure. Without applications and developers using those resources, additional technical capacity would have limited economic impact.

That makes the JAM transition both a technical and an execution challenge.

Demand for DOT-related products has also developed through other channels. In March 2026, Blockonomi reported that 21Shares had launched TDOT, described as the first U.S. spot Polkadot ETF, on Nasdaq. The product gives American investors regulated exposure to DOT while JAM is still being developed. Blockonomi’s report on the launch is available here.

Why Migration Is Harder Than Building JAM

Migrating critical components of a production blockchain is more difficult than building a new blockchain from scratch. Polkadot already has parachains, validators, applications and assets that require continued operation while the architecture changes.

The transition is therefore expected to take place gradually, in stages described in the roadmap. Before the final move to a JAM-based service for parachain finality, the role of the Relay Chain is expected to be reduced further.

That staged sequence gives observers concrete markers of progress to watch: hardening the PolkaJAM node against the hostile conditions described above, delivering the in-browser light-node library, and standing up the parachain finality service — with the network’s governance approval still required before the changes can take effect.

This approach is intended to minimize disruption and give the new infrastructure time to be tested in production. Developers will also need to provide tooling, light clients and migration processes so that applications can treat JAM as reliable infrastructure.

Even if the network performs successfully from a technical perspective, the migration would not be considered a successful upgrade if it caused unnecessary disruption to existing applications, assets or network operations.

JAM as Polkadot’s Largest Test

Polkadot has undergone major changes before, but JAM is distinct because it challenges one of the central assumptions underlying the network’s technology. Since Polkadot’s mainnet launched in 2020, the Relay Chain has been a core component of the system.

JAM proposes that many of those core architectural components can be replaced by a more flexible, programmable and service-oriented design. However, substantial engineering work remains. The production software must be hardened, parachains must receive migration paths, and the broader network must approve the changes through Polkadot’s governance process.

The major change is the level of preparation surrounding the proposal. JAM began as a technical vision described in a Gray Paper. It is now supported by production-node development, migration infrastructure and a concrete transition plan.

JAM would represent Polkadot’s most significant upgrade since launch, marking the network’s transition from a theoretical design proposal to an active engineering project that Polkadot will eventually need to implement.

This article was originally published by Blockonomi.