Polkadot 2.0 Explained: Agile Coretime and What It Changes for Developers

Polkadot 2.0 replaces the old two-year slot auction model with Agile Coretime, a flexible system that lets developers buy network compute time on a monthly basis or even block by block. This change went live in September 2024 and was finalized with the release of Polkadot SDK version 2509 in October 2025, completing the three-pillar Polkadot 2.0 upgrade alongside Asynchronous Backing and Elastic Scaling.

For developers, the practical difference is significant: launching a parachain no longer requires locking up large amounts of DOT for years at a time. You pay for what you use, when you need it.

What Was Wrong with the Old Parachain Slot System?

Before Polkadot 2.0, projects that wanted to run a parachain (a custom blockchain that plugs into Polkadot's shared security) had to win a slot through a candle auction. Those auctions required teams to lock DOT tokens for lease periods of up to two years. Only the highest bidders secured a spot.

This created real barriers:

• Small and mid-size teams needed to raise or hold massive amounts of DOT just to get started.
• Once a slot was won, the team paid for continuous blockspace whether or not they were using it.
• If a project's traffic was low for a few months, it was still burning through its lease.
• New projects with promising ideas but limited capital were simply priced out.

The auction model also created unpredictable costs. Project budgets depended on DOT's market price at the time of the auction, introducing a layer of financial risk that had nothing to do with the actual work of building.

How Does Agile Coretime Actually Work?

In Polkadot's architecture, a "core" is the virtual abstraction of computing power that the Relay Chain provides to secure a parachain's blocks. Think of it as a processing slot. Agile Coretime is the system that controls how those cores get assigned and purchased.

There are two main ways to obtain coretime today:

• Bulk coretime: A team buys access to a core for a fixed period, up to 28 days, represented as an NFT on the Coretime Chain. This is suitable for parachains that need to produce blocks continuously, such as every 6 or 12 seconds. Renewal orders take priority over new orders, which protects active chains from price spikes.
• On-demand coretime: A team pays per block, each time they need one produced. This suits projects with irregular traffic, test deployments, or applications that only need to process transactions occasionally.

Bulk coretime can also be split and resold on secondary markets, which means a team running a lighter workload can divide its core allocation and sell unused portions to other projects. This creates a more efficient use of network capacity overall.

Eskimor, lead developer at Parity Technologies, described: 

"Agile Coretime is a huge milestone in making the high quality blockspace Polkadot offers more accessible. With this and other features we have in the pipeline, I expect more experimentation and awesome projects to be launched on Polkadot."

What Are the Other Pillars of Polkadot 2.0?

Agile Coretime is one piece of a three-part upgrade. Understanding how all three work together matters for developers assessing the platform.

Asynchronous Backing

Asynchronous Backing changed how parachain blocks are validated. Previously, each parachain block had to be fully validated before the next one could start. The async model decouples those stages, allowing parachain block preparation and relay chain inclusion to happen in parallel. The result is that block times dropped from 12 seconds to 6 seconds, roughly doubling throughput for chains running on Polkadot.

Elastic Scaling

Elastic Scaling, completed in October 2025, allows a parachain to temporarily use multiple cores at the same time when demand is high, then release them when traffic drops. A chain that normally runs on one core can burst to two, three, or more during a spike. Early projections suggest individual parachains could theoretically handle hundreds of thousands of transactions per second under this model.

Together, these three upgrades form what the Polkadot community calls the "scaling trilogy," and they all converged in the Polkadot SDK 2509 release.

What Does This Mean for Developers in Practice?

The most direct change is cost structure. Instead of locking millions of dollars worth of DOT into a two-year lease, a new project can buy a single month of bulk coretime to start. If the project grows, it renews and scales up. If it shrinks or pivots, it scales back or sells unused coretime.

Builders can also mix and match:

• Reserve bulk coretime for steady workloads where consistent block production matters.
• Use on-demand coretime for testing, low-traffic phases, or applications with predictable low frequency.
• During traffic spikes, elastic scaling allows temporary expansion across multiple cores without a new contract or auction.

This flexibility is especially useful for use cases like gaming (where traffic spikes around events), DePIN (decentralized physical infrastructure networks), and AI-adjacent applications that may see highly variable load patterns.

Polkadot SDK 2509 also introduced Ethereum compatibility through Polkadot Hub, meaning Solidity smart contracts can run on Polkadot with minimal changes. Combined with PolkaVM, which supports contracts written in Rust and C++ compiled to RISC-V, developers now have multiple entry points depending on their existing skill set.

Since 2025, Polkadot has attracted 450 to 500 monthly active developers and distributes grants through an on-chain treasury that disbursed roughly $21.8 million in 2025.

What Is JAM, and Why Does It Matter?

The next major upgrade on Polkadot's roadmap is JAM, which stands for Join-Accumulate Machine. JAM is designed to replace the Relay Chain entirely with a more general-purpose architecture that treats Polkadot less like a blockchain router and more like a distributed computer. JAM enables smart contracts written in Solidity, Rust, or C++ to run across hundreds of parallel cores.

JAM was announced by Gavin Wood in April 2024. A public JAM testnet launched in January 2026, with 43 independent teams building implementations across 15 programming languages and competing for a 10 million DOT prize pool administered by the Web3 Foundation. As of June 2026, JAM is not yet live on mainnet.

The current target window for critical testing milestones and early mainnet upgrade proposals through Polkadot's OpenGov process is Q3 to Q4 2026. It builds on the same coretime model introduced in Polkadot 2.0, so the resource-purchasing mechanics that developers learn today carry forward.

DOT Tokenomics and What Changed in March 2026

A separate but related update happened in March 2026. Polkadot enacted a hard supply cap of 2.1 billion DOT and cut annual token issuance by 53.6%. This mirrors Bitcoin's supply-capping approach and was designed to reduce long-term sell pressure on the token.

Alongside the supply cap, Polkadot also overhauled how protocol revenue is handled. Previously, a portion of DOT from coretime sales was burned. That changed in January 2026 when Polkadot's governance passed the Dynamic Allocation Pool (DAP) proposal. 

Under the DAP model, coretime sales revenue, transaction fees, and validator slashes no longer get destroyed. Instead, they flow into a governance-controlled pool that allocates funds to validators, nominators, the treasury, and a strategic reserve. The practical result is that network revenue is now recycled back into the ecosystem rather than removed from circulation entirely.

As of June 2026, DOT is trading around $0.94, down significantly from 2025 highs. The first U.S. spot DOT ETF, the 21Shares TDOT, launched in March 2026, though early inflows have remained modest.

Conclusion

Polkadot 2.0 is fully deployed. Agile Coretime, Asynchronous Backing, and Elastic Scaling are live on mainnet as of the SDK 2509 release in October 2025. Together, they give developers a credible toolkit: flexible blockspace pricing, six-second block times, and the ability to scale compute capacity up and down in real time. 

JAM is the next step, currently in public testnet with a mainnet governance proposal expected in Q3 to Q4 2026. It extends the same coretime model to a broader execution environment. The infrastructure is in place; what happens next depends on developer adoption.

Resources

1. Polkadot Developer Docs – Agile Coretime – Official reference for bulk coretime and on-demand coretime mechanics on Polkadot.
2. Polkadot Wiki – Agile Coretime (Scheduling) – Deep dive into coretime scheduling, multi-threading, and bulk purchase mechanics.
3. Parity Technologies – Polkadot Upgrade 2025: What You Need to Know – Overview of SDK 2509, Asynchronous Backing, Agile Coretime, and Elastic Scaling from Polkadot's core development team.
4. Polkadot Newsroom – Polkadot Launches Agile Coretime – Official press release with developer commentary from Parity Technologies.
5. OneKey Blog – What's Next for Polkadot: Upcoming Upgrades and Milestones for 2025-26 – Summary of coretime market development, JAM roadmap, and developer strategy for 2025-26.
6. Polkadot Developer Docs – Obtain Coretime – Practical guide for purchasing bulk and on-demand coretime when deploying a parachain.
7. Elastic Scaling – Polkadot Developer Docs – Technical documentation for multi-core parallel execution on Polkadot.
8. Parity Technologies – Refining Polkadot's Economic Architecture: DOT Issuance, DAP, and Network Adjustments – Official explanation of the Dynamic Allocation Pool, the 2.1 billion DOT supply cap, and the March 2026 issuance reduction.