> For the complete documentation index, see [llms.txt](https://bootcamp.openguild.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bootcamp.openguild.wtf/building-a-blockchain-with-polkadot-sdk/polkadot-sdk/cumulus/agile-coretime.md).

# Agile Coretime

<figure><img src="/files/rdZ8SZBwO6mkzVqm1jyz" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/QNqttwxfAX82XPfHfL3C" alt=""><figcaption></figcaption></figure>

In Polkadot 1.0, the only way for a parachain to be secured by Polkadot was to rent a lease through an [auction](https://wiki.polkadot.network/docs/learn/learn-auction), which guaranteed parachain block validation for up-to two years. This involved locking significant amount of DOT, leading to a high barrier of entry for small and medium scale blockchain projects. The parachains produced blocks at a regular interval of 12 seconds, irrespective of the network activity. This led to inefficient resource allocation and misplaced economic incentives while producing almost empty blocks under lighter traffic and being unable to accommodate heavier traffic when it exceeded block limits. Agile Coretime resolves all of these drawbacks.

The figure below shows the core usage for Polkadot 1.0, where the horizontal axis is time, and each row represents a core. Colors show different parachains, each using one core (i.e., one parachain, one core).

<figure><img src="/files/7HxIX6DzELL2TlNrdWwx" alt=""><figcaption></figcaption></figure>

Agile Coretime allows for the purchase of [coretime](https://wiki.polkadot.network/docs/learn-agile-coretime#coretime) in “bulk” with an allocation for one month. Heavy duty parachains which need to author a block every 12 seconds (or every 6s through [Asynchronous Backing](https://wiki.polkadot.network/docs/learn-async-backing)), can seamlessly “renew” the [core](https://wiki.polkadot.network/docs/learn-agile-coretime#core) each month. Coretime renewal orders take precedence over new orders and provide protection against price fluctuations, allowing parachains to plan their project budget and costs more effectively.

The purchased coretime can also be split up and sold in parts, down to a single block per month, allowing for secondary markets to thrive and improve the allocation efficiency of coretime. Furthermore, Agile Coretime offers [on-demand coretime](https://wiki.polkadot.network/docs/learn-agile-coretime#on-demand-coretime) functionality that enables the authoring of a parachain block on-demand.

<figure><img src="/files/t993blcXJ2T1rGlRXUym" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bootcamp.openguild.wtf/building-a-blockchain-with-polkadot-sdk/polkadot-sdk/cumulus/agile-coretime.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.