Coretime

TL;DR One year after Polkadot 2.0 shipped its three flagship pieces - Agile Coretime, Elastic Scaling, and Asynchronous Backing - the picture is mixed but mostly positive. What worked: core prices collapsed, network utilization roughly doubled, and the barrier to entry is now hundreds of dollars instead of millions. New teams are shipping that would never have run a crowdloan. What did not: the secondary market for cores is thin, bulk sales are dominated by a small set of repeat bidders, and the developer story for “buy a core and ship something” is still rougher than it should be. The honest verdict: Agile Coretime delivered on the economics. It did not deliver on the user-experience promise. Polkadot 2.0 is a better foundation than Polkadot 1.0 by every measurable metric, but the application layer is still where the network has to prove itself. Where We Were A Year Ago Last September I wrote a plain-English explainer of Agile Coretime. The pitch was simple: stop selling parachain slots like reserved parking spaces and start selling them like a parking meter. Pay for what you use, when you use it. Resell what you do not. ...

If you’ve been following Polkadot, you’ve probably heard “Agile Coretime” mentioned alongside “Elastic Scaling” and “Asynchronous Backing.” It sounds technical, important, and confusing. This post explains what it actually is, why it matters, and what it means for the network. The short version: Polkadot used to allocate blockspace like reserved parking spots. Agile Coretime makes it more like a parking meter - you pay for what you use, when you use it. ...