Dynamic Pricing for Bulk Coretime Sales #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
FWIW, the rules in #2 (currently being voted on as Fellowship Referendum 7) state that anyone may open an RFC , invitation or not :) |
rphmeier
reviewed
Jul 11, 2023
|
|
||
| ## Motivation | ||
|
|
||
| RFC-1 proposes periodic Bulk Coretime Sales as a mechanism to sell continouos regions of blockspace (suggested to be 4 weeks in length). A number of Blockspace Regions (compare RFC-1 & RFC-3) are provided for sale to the Broker-Chain each period and shall be sold in a way that provides value-capture for the Polkadot network. The exact pricing mechanism is out of scope for RFC-1 and shall be provided by this RFC. |
There was a problem hiding this comment.
RFC-3 is a companion to RFC-1, for underlying improvements to scheduling infrastructure - the goal is for them to communicate via RFC-5. But it's probably out of scope for anything related to pricing/sales
There was a problem hiding this comment.
was that just a comment on the relationship of the RFCs or should I change something?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RFC-1 asks for another RFC that specifies the pricing function of Bulk Coretime Sales. RFC-6 is a proposal to apply a dynamic pricing function that has several levers for governance to adapt the pricing curve to changing market conditions.
This RFC follows a proposal in the Polkadot Forum here and an invitation by Gavin Wood to submit an RFC here.
ToDos: