-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Create a parathread auction module for collators to bid on parathread slots #1512
Comments
As I'm reading through this, I find myself getting more and more confused. What does this line even mean? polkadot/runtime/common/src/registrar.rs Line 616 in 3b62357
That sure looks like it's using a function call as the receiver of an |
Guessing that this has to do with macro magic by which If I'm reading the code properly, the registrar code didn't actually implement any kind of priority queue selection mechanism which would make it an auction; it was more of a first-come, first-served parathread registration thing. This leads to two questions:
|
@coriolinus you are correct that this is both an enum variant and a function name. Something that is mostly needed to get a complete list of the possible functions in a module. We then use this information to dispatch a call to the right function. So the extrinsic will say: "Module 1, Extrinsic 3", and we will look at the enum for module 1, and the 3rd item in the enum. The way the auction works is through the "priority" of the tx. The TX queue order txs by priority, and one direct way a user can increase their priority is including a So users who want to make their way into the auction must have the highest tip, thus forming a 1 block auction. I talk about this at a high level including the signed extension here: https://youtu.be/95Ji5u0q3AU?t=1004 |
@shawntabrizi Thanks for the link! Watching that now. |
oops wrong auction thread for my comment here.. ;) |
@shawntabrizi still needed? |
Yes, it is needed. I can own this if needed at the appropriate time for implementation. |
paritytech/polkadot-sdk#828 outdates this |
This functionality was already implemented as a
SignedExtension
in the old Registrar prior to #1501. The same logic should be ported over here, except wrapping around theParas
andScheduler
modules. This should live inpolkadot-runtime-common
as it is "glue" code and not core code.The text was updated successfully, but these errors were encountered: