Enum polkadot_node_subsystem::messages::CandidateValidationMessage

pub enum CandidateValidationMessage {
    ValidateFromChainState(CandidateReceipt<H256>, Arc<PoV>, Duration, Sender<Result<ValidationResult, ValidationFailed>>),
    ValidateFromExhaustive(PersistedValidationData<H256, u32>, ValidationCode, CandidateReceipt<H256>, Arc<PoV>, Duration, Sender<Result<ValidationResult, ValidationFailed>>),
    PreCheck(H256, ValidationCodeHash, Sender<PreCheckOutcome>),
}

Messages received by the Validation subsystem.

Validation Requests

Validation requests made to the subsystem should return an error only on internal error. Otherwise, they should return either Ok(ValidationResult::Valid(_)) or Ok(ValidationResult::Invalid).

Variants

ValidateFromChainState(CandidateReceipt<H256>, Arc<PoV>, Duration, Sender<Result<ValidationResult, ValidationFailed>>)

Tuple Fields

0: CandidateReceipt<H256>

1: Arc<PoV>

2: Duration

Execution timeout

3: Sender<Result<ValidationResult, ValidationFailed>>

Validate a candidate with provided parameters using relay-chain state.

This will implicitly attempt to gather the PersistedValidationData and ValidationCode from the runtime API of the chain, based on the relay_parent of the CandidateReceipt.

This will also perform checking of validation outputs against the acceptance criteria.

If there is no state available which can provide this data or the core for the para is not free at the relay-parent, an error is returned.

ValidateFromExhaustive(PersistedValidationData<H256, u32>, ValidationCode, CandidateReceipt<H256>, Arc<PoV>, Duration, Sender<Result<ValidationResult, ValidationFailed>>)

Tuple Fields

0: PersistedValidationData<H256, u32>

1: ValidationCode

2: CandidateReceipt<H256>

3: Arc<PoV>

4: Duration

Execution timeout

5: Sender<Result<ValidationResult, ValidationFailed>>

Validate a candidate with provided, exhaustive parameters for validation.

Explicitly provide the PersistedValidationData and ValidationCode so this can do full validation without needing to access the state of the relay-chain.

This request doesn’t involve acceptance criteria checking, therefore only useful for the cases where the validity of the candidate is established. This is the case for the typical use-case: secondary checkers would use this request relying on the full prior checks performed by the relay-chain.

PreCheck(H256, ValidationCodeHash, Sender<PreCheckOutcome>)

Try to compile the given validation code and send back the outcome.

The validation code is specified by the hash and will be queried from the runtime API at the given relay-parent.

Trait Implementations

impl AssociateOutgoing for CandidateValidationMessage

type OutgoingMessages = CandidateValidationOutgoingMessages

The associated outgoing messages for a subsystem that consumes the message Self.

impl Debug for CandidateValidationMessage

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl From<CandidateValidationMessage> for AllMessages

fn from(message: CandidateValidationMessage) -> AllMessages

Converts to this type from the input type.

impl From<CandidateValidationMessage> for ApprovalVotingOutgoingMessages

fn from(message: CandidateValidationMessage) -> ApprovalVotingOutgoingMessages

Converts to this type from the input type.

impl From<CandidateValidationMessage> for CandidateBackingOutgoingMessages

fn from(message: CandidateValidationMessage) -> CandidateBackingOutgoingMessages

Converts to this type from the input type.

impl From<CandidateValidationMessage> for DisputeCoordinatorOutgoingMessages

fn from( message: CandidateValidationMessage ) -> DisputeCoordinatorOutgoingMessages

Converts to this type from the input type.

impl From<CandidateValidationMessage> for PvfCheckerOutgoingMessages

fn from(message: CandidateValidationMessage) -> PvfCheckerOutgoingMessages

Converts to this type from the input type.