-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic Pricing for Bulk Coretime Sales #6
base: main
Are you sure you want to change the base?
Dynamic Pricing for Bulk Coretime Sales #6
Conversation
FWIW, the rules in #2 (currently being voted on as Fellowship Referendum 7) state that anyone may open an RFC , invitation or not :) |
|
||
## 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was that just a comment on the relationship of the RFCs or should I change something?
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: