pub trait SchedulingV3EnabledApi<Block: BlockT>: Core<Block> {
// Provided method
fn scheduling_v3_enabled(
&self,
__runtime_api_at_param__: <Block as BlockT>::Hash,
) -> Result<bool, ApiError> { ... }
}Expand description
API to tell the node side whether V3 scheduling is enabled.
When enabled, collators must produce V3 candidates with:
- ParachainBlockData::V2 containing the scheduling proof
- CandidateDescriptorV3 with scheduling_parent
This is mutually exclusive with relay parent offset (building on older relay parents). A parachain enables V3 when it wants low-latency block production with the dual-parent model.