Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Polkadot’s parachain economy is the system for allocating relay-chain computing time and shared security to connected chains. Today, non-system chains access that capacity by buying Agile Coretime in bulk or on demand; the former competitive lease auctions and crowdloans are historical, not the current onboarding route. System chains receive execution cores through governance.

What is a Polkadot parachain?

A parachain is an independent, chain-like application structure connected to Polkadot’s relay chain. The relay chain coordinates validators, core scheduling, data availability, and shared security, while most application-specific behavior lives on the connected chain. Parachain validators validate its state transitions, and the chain shares the relay chain’s security assumptions. Polkadot’s architecture documentation notes that a relay-chain revert would affect connected parachains too, maintaining system-wide consistency.

“Parachain” does not mean “a chain that must have its own token.” The Polkadot Wiki says parachains are not required to issue a token; whether to create one is a decision for the chain team. Access to relay-chain computation and interoperability also does not guarantee a project’s commercial success or the value of any token.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What is Agile Coretime?

A core is a virtual execution resource on Polkadot; coretime is the time allocated to use one. Agile Coretime is the current way non-system chains obtain that resource: they can purchase a fixed period of coretime in bulk or buy it on demand when needed. The official documentation describes coretime as a more flexible alternative to reserving a core through a long lease.

#1 Best Overall
Polkadot Crypto Polkadot Cryptocurrency Hardcover Journal, Black
  • Polkadot Crypto Polkadot Cryptocurrency Eat Sleep Polkadot Repeat
  • Polkadot Crypto Polkadot Cryptocurrency Eat Sleep Polkadot Repeat
  • Hardcover journal with 240 line-ruled pages (120 sheets)
  • Built-in elastic closure and ribbon bookmark
  • Includes an expandable inner storage pocket and a pen holder

For non-system chains, coretime is purchased with DOT, and the Wiki says the purchase tokens are burned. This describes the documented payment mechanism, not a current DOT price or a claim about DOT’s investment value. The two purchase routes differ mainly in access pattern and price predictability:

Decision factor Bulk coretime On-demand coretime
Access pattern Coretime assigned for a fixed period. Coretime ordered as needed.
Price behavior Purchase price and renewal pricing are predictable under the official guide. Variable spot price that may depend on demand and other market conditions.
Planning fit More suitable to plan around when a chain expects sustained, regular relay-chain access. May suit intermittent or uncertain block-production needs.
Cost uncertainty Lower uncertainty over the purchase period. More exposure to changing prices and demand.

These are qualitative differences, not a promise that one option is always cheaper. Which route makes sense depends on how regularly a chain needs execution time and how much price variability it can accommodate. Polkadot’s design documentation also describes coretime as potentially splittable or interlaced in some cases; that is a design capability, not evidence of independently measured cost savings.

How do system chains get execution cores?

System chains perform network-level functions rather than operating like typical application-specific chains. Examples include assets, identity, governance, and bridging. Governance allocates their execution cores, instead of requiring them to purchase coretime through the same mechanism used by non-system chains. The Wiki says system chains generally do not have a native token or a governance system separate from DOT.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What happened to parachain auctions and crowdloans?

Under the former model, teams competed in lease auctions for a core. Crowdloans let teams seek tokens from supporters to participate in those auctions. That process is no longer the current route to core access: Polkadot’s guide says lease auctions stopped on-chain on 19 September 2024, when runtime upgrade 1.2.0 was enacted.

At the transition, active leases were automatically converted to bulk coretime. Leases that had not started were canceled, and their locked tokens were refunded. Those transition details are historical; they should not be confused with present-day bulk coretime purchases.

When does on-demand coretime fit?

On-demand parachains, previously called parathreads, can connect intermittently by purchasing coretime for blocks as required. This avoids paying to occupy a dedicated core continuously when a chain does not need one or cannot justify the ongoing commitment. The trade-off is that on-demand access uses a variable spot price, so planning costs may be less predictable than with a fixed-period bulk purchase.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What does the parachain economy mean for DOT?

DOT has a direct role in the documented coretime mechanism because non-system chains use it to purchase bulk or on-demand coretime, and the Wiki says those purchase tokens are burned. System-chain cores, by contrast, are allocated through governance. The available documentation does not establish a live coretime price, average market cost, or an economic-impact figure, so no current price or market-size claim should be inferred from the mechanism alone.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What builders should check before choosing a route

  • Estimate whether relay-chain execution is needed continuously or only for intermittent block production.
  • Compare the predictability of a fixed-period bulk purchase with the variable spot pricing of on-demand coretime.
  • Check the current network rules, prices, governance allocations, and purchase availability before committing; these can change.
  • Polkadot Wiki names RegionX Hub for coretime overview, purchase, and management, and Lastic as a marketplace describing transfers, splits, and assignments. These are third-party interfaces, so verify their current availability and functions before relying on them.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.