Module scheduling 

V3 scheduling types for low-latency parachain block production.

V3 candidates separate the relay parent (execution context) from the scheduling parent (a recent relay chain tip used for core assignment). This enables building on older relay parents while still being scheduled based on recent relay state.

Resubmission

When a candidate fails to get backed in time, a different collator can resubmit it with a new scheduling_parent (fresh relay tip) without re-executing the blocks. The relay_parent stays the same since the execution context hasn’t changed.

For resubmission, signed_scheduling_info must be provided. The resubmitting collator signs the core selection, proving they are the eligible author for the slot derived from the internal_scheduling_parent.

Structs

SchedulingInfoPayload

Payload signed by a collator for resubmission.

SchedulingProof

V3 scheduling proof included in the POV.

SignedSchedulingInfo

Signed scheduling information for candidate resubmission.

Traits

VerifySchedulingSignature

Verifier for V3 scheduling.