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 tip used for core assignment), so blocks can build on older relay parents while still being scheduled off recent relay state.

Resubmission

If a candidate isn’t backed in time, another collator can resubmit it with a fresh scheduling_parent — same relay_parent, no re-execution — by providing a signed_scheduling_info proving it is the eligible author for the slot at internal_scheduling_parent.

Structs

SchedulingInfoPayload

Payload a collator signs to resubmit a candidate.

SchedulingProof

V3 scheduling proof included in the PoV.

SchedulingSignals

The scheduling-signal tail (SelectCore/ApprovedPeer) a candidate emits after the first UMP_SEPARATOR.

SignedSchedulingInfo

Signed scheduling info for candidate resubmission: a SchedulingInfoPayload plus the collator’s signature over it, proving eligibility for the slot at internal_scheduling_parent.

Traits

VerifySchedulingSignature

Verifier for V3 scheduling: reports whether V3 is enabled and verifies a candidate’s SignedSchedulingInfo.