Blockspace is the capacity a blockchain has to process transactions. Polkadot Agile Coretime changes how that capacity is sold.
Before, projects competed in slot auctions for long parachain leases. Now they buy time on Polkadot's shared security, in bulk or one block at a time.
This guide explains how Polkadot Agile Coretime works and what changes for developers. Facts come from Polkadot's official documentation, whose core-time page was last updated on 29 June 2026.
Polkadot Agile Core-time is the scheduling system that lets parachains use Polkadot's cores. A core is a virtual slice of computing power. A randomized group of relay chain validators uses it to check a parachain's blocks.
Coretime is the time a core is assigned to a task, counted in relay chain blocks. Blockspace is the resource. Coretime is how Polkadot measures and sells it.
The official Polkadot documentation describes two routes: continuous bulk coretime and dynamic on-demand coretime.
Polkadot 1.0 had one way in. A parachain won a lease auction, which secured block validation for up to two years.
That meant locking a large amount of DOT. Small teams often could not afford it.
Waste was the other problem. Parachains produced blocks every 12 seconds whatever the traffic. Quiet chains made nearly empty blocks. Busy chains hit limits.
Polkadot Agile Coretime is part of the Polkadot 2.0 changes built to fix both issues.
Picture a core as a lane and coretime as the hours you hold it. During that window, the assigned parachain gets its blocks validated.
Miss the window and the chain stops. Unused time cannot be carried over.
Buyers get coretime through the Coretime Chain, a system parachain that runs sales and schedules cores. Polkadot's developer docs include a coretime purchase guide for the practical steps.
Bulk coretime is a fixed stretch of continuous core access. Under Polkadot Agile Coretime it currently lasts 28 days and is bought with DOT.
Each purchase is a region, an NFT that can be split, shared or resold. That makes coretime a tradable asset.
A region assigned to one parachain can take a price-capped renewal. It works like rent control and helps teams forecast costs. Splitting, interlacing or leaving the region idle removes that right.
On-demand coretime is the pay-as-you-go option. Polkadot keeps dedicated cores for it, separate from bulk-sales. Parachains pay in DOT per block.
Polkadot's wiki says the price has a floor and rises with the queue. That suits variable workloads such as prototypes or apps with occasional activity.
Payment is in DOT, part of the Polkadot tokenomics model that also covers fees, staking and governance deposits.
Feature | Bulk Coretime | On-Demand Coretime |
Access | Extended period (28 days) | Per block |
Use case | Continuous workloads | Variable workloads |
Payment | Bulk purchase in DOT | Pay as needed in DOT |
Flexibility | High | Very high |
Steady traffic points toward bulk. Uneven traffic points toward on-demand.
Polkadot's wiki says auctions ran until Polkadot Agile Coretime launched on 19 September 2024. Ongoing auctions were canceled, and active leases were migrated with renewal rights.
The result looks more like a marketplace. Smaller projects can start on-demand. Steady chains can buy bulk-time. Spare time can be resold, so fewer cores sit idle.
It also sits alongside Polkadot's wider plans, including the JAM upgrade.
Splitting divides a region into contiguous time pieces. A chain that needs steady blocks but not a full 28 days keeps only the part it needs.
Interlacing divides a region by block. Several parachains take turns producing blocks in the same window. That fits low-traffic chains.
The trade-off is renewal. Split or interlaced regions lose the price cap. Polkadot's wiki has a coretime terminology list for each term.
The Coretime Chain runs the broker pallet, the code that manages coretime. Its jobs include:
Running bulk sales and renewals
Tracking regions as NFTs, including transfers and task assignment
Pooling cores for on-demand use
Telling the relay chain which task runs on each core
It announces core schedules 80 relay chain blocks ahead.
Flexible access: on-demand core time lowers the entry barrier.
Cost predictability: bulk renewals are price-capped.
Efficient use: chains pay for time they use, and idle time can be resold.
Easier scaling: elastic scaling, still under development per the docs, would let one parachain use several cores.
The model is not risk-free for builders.
Pricing: bulk prices react to earlier sales. The starting price and ideal bulk ratio are set through Polkadot OpenGov governance.
Demand swings: on-demand prices rise as the queue grows.
Unused time: idle core time is lost unless resold.
Learning curve: regions, timeslices and renewals take time to learn.
Factor | Old Slot Auctions | Agile Coretime |
Access mechanism | Lease auction | Coretime sales or per-block orders |
Cost structure | Large DOT amount locked | DOT paid for time used |
Duration | Up to two years | 28 days bulk, one block on-demand |
Flexibility | Fixed lease | Regions split, shared or resold |
Resource use | Blocks every 12 seconds regardless | Time assigned by demand |
New teams can start on-demand and move to bulk as traffic grows. Existing parachains had leases migrated, then renewed like other bulk buyers.
High-traffic apps benefit from bulk renewal. Low-traffic apps can use on-demand or interlaced time. Parachains still talk to each other through XCM cross-chain messaging, which is separate from how they buy core-time.
For developers, Polkadot Agile Coretime mostly means budgeting by time rather than by lease.
Slot auctions priced blockspace by how much capital a team could lock. Polkadot Agile Core-time prices it by time used. That makes blockspace behave more like a utility bill than a property purchase.
One link is worth watching. The wiki says coretime sales revenue is burned. If demand grows, more DOT could be removed from supply. That is a possible effect, not a certainty.
Polkadot Agile Coretime replaces lease auctions with a time-based market for blockspace. Bulk coretime offers 28-day predictability, and on-demand coretime offers per-block flexibility.
What remains uncertain is how prices behave as demand changes, and when elastic scaling arrives. Check current core time prices and sale status in Polkadot's official documentation.
Disclaimer: This article is for information only and is not financial or investment advice. Crypto assets are volatile and carry risk, and coretime prices or protocol settings may change. Do your own research before making any decision.