Update July 23: Filter the on-demand extrinsics on the relay. Retire on-demand credits. Users will buy and assign coretime with DOT on the Coretime chain when needed. This adds latency but is compatible with JAM.
Context
As part of prepping the RC for JAM, all user-facing functionality must be removed from the Relay Chain. Bulk coretime already lives entirely on the Coretime chain, but on-demand coretime ordering is still driven by user-callable extrinsics on the RC (place_order_* in the on_demand pallet, polkadot-runtime-parachains).
Requirement
User interaction for on-demand coretime must move out of the RC on-demand pallet and onto the Coretime chain. After this work:
- Users can still purchase on-demand coretime.
- There is no user-callable extrinsic for on-demand ordering on the RC.
- Existing on-demand users (collators) experience no loss of functionality.
Keep
The on-demand queue and scheduler stay on the RC. Only the user-facing entry point (payment + order submission) moves.
Scope
This issue only adds the CT ordering path. Blocking the RC on-demand calls is handled separately via call filters. So at the end of this work, ordering is possible from both the RC and CT -- that is expected and fine.
Update July 23: Filter the on-demand extrinsics on the relay. Retire on-demand credits. Users will buy and assign coretime with DOT on the Coretime chain when needed. This adds latency but is compatible with JAM.
Context
As part of prepping the RC for JAM, all user-facing functionality must be removed from the Relay Chain. Bulk coretime already lives entirely on the Coretime chain, but on-demand coretime ordering is still driven by user-callable extrinsics on the RC (
place_order_*in theon_demandpallet,polkadot-runtime-parachains).Requirement
User interaction for on-demand coretime must move out of the RC on-demand pallet and onto the Coretime chain. After this work:
Keep
The on-demand queue and scheduler stay on the RC. Only the user-facing entry point (payment + order submission) moves.
Scope
This issue only adds the CT ordering path. Blocking the RC on-demand calls is handled separately via call filters. So at the end of this work, ordering is possible from both the RC and CT -- that is expected and fine.