# Initial Coretime Pricing

**URL:** <https://forum.polkadot.network/t/initial-coretime-pricing/5187>\
**Category:** Governance\
**Created:** [December 8, 2023, 4:11pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187 "2023-12-08T16:11:50Z")\
**Posts on this page:** 12\
**Page:** 2

<div class="post-metadata">

**Author:** ![phillux](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/phillux/32/2347_2.png) [@phillux](https://forum.polkadot.network/u/phillux)\
**Post date:** [February 6, 2024, 3:45pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/22 "2024-02-06T15:45:49Z")

</div>

> [@jelliedowl](#):
>
> > Comparing to the average of $16,000 USD/month for locking, it has been assumed that ca. $1000/month is still much cheaper even when factoring in opportunity cost.
> 
> That might be the case on Polkadot - I’m completely priced out of that so I don’t even bother looking. On Kusama, that’s not the average, and the slots can be had for essentially nothing if you aren’t in a hurry. Most chains “pay” a nominal 10 - 100KSM.
> 
> My parachain is essentially running on nothing (and not doing much right now - so there’s a legitimate argument that it’s not a good example), but there are other chains that are doing more on Kusama and also don’t really have lots of money to spare. It seems likely (to me) that any substantial lease charge will kill them off.

With regards to Kusama, you may be correct and this is something we should be mindful of. It does seem a bit disproportional from Polkadot if we look at the cost of locking DOT for parachains on Polkadot vs the cost of locking KSM for parachains on KSM. @erin Perhaps we need a more friendly approach on Kusama?

Also @jelliedowl, the price _does_ adjust month to month, so if the offered cores don’t meet demand the price will drop for the following month’s sales. You can play around with this using [Lastic’s Coretime Price Simulator](https://lastic.streamlit.app/).

> [@jelliedowl](#):
>
> I was actually thinking, the other day, about raising a proposal to “award” a parachain with a registration / initial code upload / lease to experiment with - primarily to test the water for that as a model. At the moment, I don’t have time to come up with an experimental parachain concept to pitch for though. To an extent, it comes down to what level / number of bootstrapped experiments Kusama is willing to support - I think they should welcome such things, but on-chain governance can be pretty conservative.

There will be a system called “[Coretime credits](https://github.com/paritytech/polkadot-sdk/issues/2998)” but I’m not sure how they will be distributed. Maybe @bkchr could shed some light on this?

> [@jelliedowl](#):
>
> (EDIT: I’m also clearly incapable of tagging a message as replying to another one - not sure what I’m not getting about the UI.)

Took me a while to find too. Once you click “reply” there’s a little quote bubble in the upper-left of the toolbar.  
 ![image](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/7/78edb85d268405d5d7d9215c61526b5b8b1ad28e.png)

---

<div class="post-metadata">

**Author:** ![jelliedowl](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@jelliedowl](https://forum.polkadot.network/u/jelliedowl)\
**Post date:** [February 6, 2024, 3:53pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/23 "2024-02-06T15:53:47Z")

</div>

> [@phillux](#):
>
> Took me a while to find too. Once you click “reply” there’s a little quote bubble in the upper-left of the toolbar.

Aha! I was using block quotes before - thanks!

And all else is good - ultimately, it’s all part of iterating to the correct answer.

---

<div class="post-metadata">

**Author:** ![erin](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/erin/32/156_2.png) [@erin](https://forum.polkadot.network/u/erin)\
**Post date:** [February 6, 2024, 3:55pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/24 "2024-02-06T15:55:59Z")

</div>

> [@erin](#):
>
> `* (1.8%) * (2sec/5MB)`

You can take this part of the equation for Polkadot and change the expected weight percentage of the block as a variable. The current median for Kusama blocks is also 1.8%, so this can be tweaked anywhere from 1.8%-100% to find a value. This would mean going with the validator fee calculation, unless the average of the infrastructure calculation and the validator fee calculation is used. For Kusama using the median 1.8% results in .662 KSM (without locking opportunity cost discount) or .66 KSM (with discount). The average block weight is 13% (as there is quite a bit of variability over chains) which would result in 4.41 KSM without discount or 4.39 KSM with discount.

I should note, for this calculation I used the current average of Kusama validator rewards of .91 KSM per era/3.64 KSM a day rather than my estimate of 2 KSM in the original post (the rest of the numbers were confirmed besides this one - I didn’t have it until today).

---

<div class="post-metadata">

**Author:** ![pdmerritt](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/pdmerritt/32/3795_2.png) [@pdmerritt](https://forum.polkadot.network/u/pdmerritt)\
**Post date:** [February 16, 2024, 5:18pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/25 "2024-02-16T17:18:21Z")

</div>

I see some of you doing all these formulas and other methods to figure out core time pricing. But maybe you should look at it differently. Think in a business perspective…Dot is NOT the only blockchain out there there are tons of them and they are all competing and all of them have a suite of similar products. How do new businesses typically lure new customers in amidst all the competition? They incentivise!!! Core time price should imho undercut the cost of whatever it costs to establish your average L1 on any of the popular platforms. On top of that there should be discounts for projects that buy in bulk. Maybe even free technical assistance in getting setup. THIS WILL BRING PRODUCTS TO POLKADOT!!! Not related to Coretime but dot holders NEED to be incentivised as well…staking alone isn’t enough. Projects should be encouraged to do air drops…solana, avalanche, cosmos etc. are killing dot because of all those airdrops and incentives. While dot still sitting on it’s hands and watching the marketcap get smaller and smaller. Heck maybe projects could get a discount on coretime if they agree to airdrop dot holders. But something NEEDS to change to get Polkadot back on track!!!

---

<div class="post-metadata">

**Author:** ![eskimor](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/eskimor/32/6264_2.png) [@eskimor](https://forum.polkadot.network/u/eskimor)\
**Post date:** [March 5, 2024, 8:06pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/26 "2024-03-05T20:06:03Z")

</div>

@phillux Some discussion on the lead-in factor [here](https://github.com/polkadot-fellows/runtimes/pull/212#discussion_r1512480014). We lean towards keeping it at 2.

---

<div class="post-metadata">

**Author:** ![tymat](https://avatars.discourse-cdn.com/v4/letter/t/c77e96/32.png) [@tymat](https://forum.polkadot.network/u/tymat)\
**Post date:** [April 3, 2024, 3:33am UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/27 "2024-04-03T03:33:36Z")

</div>

> Bulk coretime can be purchased up to 28 days in advance, and bulk renewals are capped within a percentage of the previous purchase price.

Need to take this into consideration from the Polkadot Agile Coretime website. Do we know what this percentage will be?

---

<div class="post-metadata">

**Author:** ![alice\_und\_bob](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/alice_und_bob/32/10098_2.png) [@alice\_und\_bob](https://forum.polkadot.network/u/alice_und_bob)\
**Post date:** [April 3, 2024, 8:20am UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/28 "2024-04-03T08:20:45Z")

</div>

Let’s start on Kusama cheap with 1 KSM (~50 USD) and let chaos ensue. Then gather additional data points from that.

A question that also determines price is how many cores there will be available for bulk coretime. Do we have an answer for that already?

---

<div class="post-metadata">

**Author:** ![eskimor](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/eskimor/32/6264_2.png) [@eskimor](https://forum.polkadot.network/u/eskimor)\
**Post date:** [April 3, 2024, 9:21am UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/29 "2024-04-03T09:21:02Z")

</div>

We could do that if lead\_in is high enough, but on the flip side one major point of Agile Coretime is to improve allocation efficiency. We want to encourage core sharing via secondary markets. If your application does not need a full block every 6s, you should also not use those system resources, but leave them to others, resulting in more resources being available for everybody.

My ideal eventual usage pattern would be for low-volume parachains to bulk order a reasonable amount of coretime to account for the actual block space they need on average. E.g. one block every 30s or even less, then UIs can either soft confirm actions once a transaction is in the mempool, or even build smaller blocks which will be combined into one for eventual inclusion on the relay chain, providing low latency for users, in the case of “low amount” local (non cross-chain) transactions.

To account for fast “full confirmation” needs, e.g. because a transaction moved a significant amount of funds or because a cross chain action (XCM) was triggered, the chain could order an on-demand core to provide low latency to users even in those cases.

Applications could even let the user choose, fast confirmation for XX fees, slow 30s confirmation with xx fees, where xx is obviously less than XX.

---

<div class="post-metadata">

**Author:** ![seadanda](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@seadanda](https://forum.polkadot.network/u/seadanda)\
**Post date:** [April 3, 2024, 9:21am UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/30 "2024-04-03T09:21:38Z")

</div>

I think starting too cheaply injects lots of volatility in and we actually learn less from the process, unless we aim to use the same high-volatility strategy with polkadot. I still think that our absolute best guess of a reasonable initial price combined with a conservative pricing model is the best approach to start off.  
I think the low price approach would work well if we had lots of cores and lots of teams off lease, but with our conditions I think it could be a non-representative sample of the market.

> Need to take this into consideration from the Polkadot Agile Coretime website. Do we know what this percentage will be?

The renewal bump that is proposed in the [Kusama Coretime Chain PR](https://github.com/polkadot-fellows/runtimes/pull/212) is 3% each sale, representing a maximum of ~47% annually.

---

<div class="post-metadata">

**Author:** ![eskimor](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/eskimor/32/6264_2.png) [@eskimor](https://forum.polkadot.network/u/eskimor)\
**Post date:** [May 24, 2024, 4:50pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/31 "2024-05-24T16:50:52Z")

</div>

Update: New proposal with changed price function and a leadin factor of 100 [here](https://github.com/paritytech/polkadot-sdk/issues/4360).

Some more explanation especially on renewals can be found in [this post](https://grillapp.net/12935/agile-coretime-pricing-explained-166522?ref=12935).

---

<div class="post-metadata">

**Author:** ![phillux](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/phillux/32/2347_2.png) [@phillux](https://forum.polkadot.network/u/phillux)\
**Post date:** [May 27, 2024, 11:36am UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/32 "2024-05-27T11:36:49Z")

</div>

Happy to see @eskimor!

Thanks for taking our feedback and sharing your updates

---

<div class="post-metadata">

**Author:** ![labormedia](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/labormedia/32/2638_2.png) [@labormedia](https://forum.polkadot.network/u/labormedia)\
**Post date:** [June 11, 2025, 10:35pm UTC](https://forum.polkadot.network/t/initial-coretime-pricing/5187/33 "2025-06-11T22:35:47Z")

</div>

Hello guys,

I was trying to initiate a discussion about this without much success on the PBA Alumni chat and I was quickly directed here.

Anyways, if you stumble upon a solution to Coretime price that:

1. Detaches preference layer from settlement price deterministically,
2. Eliminates price/qty assumptions, with convex preferences (not semi-linear as has been proposed),
3. Is smooth, with differentiable price evolution curve,
4. Converges and stabilizes on a unique price,
5. Is p2p, suited for decentralized scenarios,
6. Is cheap and efficient to execute per p2p transaction,
7. Is Pareto Optimal.

Then I would love to participate in the discussion, because as far as I understand that’s what I’ve got.  
This is a project that started in the year 2000, when I was studying economics in Chile.

You can find the mathematical framework of my solution here:

> **[GitHub - onedge-network/Emergent\_Properties\_paper: Repository for the last version of the paper:...](https://github.com/onedge-network/Emergent_Properties_paper)**
>
> Repository for the last version of the paper: "Emergent Properties of Distributed Agents with Two-Stage Convex Zero-Sum Optimal Exchange Network"

[Previous page](https://forum.polkadot.network/t/initial-coretime-pricing/5187.md?page=1)
