Type Alias ReportsInput

Work Report is presented on-chain within GuaranteesExtrinsic and then it's being erasure-codec and assured (i.e. voted available by validators).

After enough assurances the work-report is considered available, and the work outputs transform the state of their associated service by virtue of accumulation, covered in section 12. The report may also be timed-out, implying it may be replaced by another report without accumulation.

https://graypaper.fluffylabs.dev/#/5f542d7/133d00134200

type ReportsInput = {
    assurancesAvailAssignment: AssurancesStateUpdate["availabilityAssignment"];
    guarantees: GuaranteesExtrinsicView;
    newEntropy: SafroleStateUpdate["entropy"];
    offenders: HashSet<crypto.Ed25519Key>;
    recentBlocksPartialUpdate: RecentHistoryStateUpdate["recentBlocks"];
    slot: TimeSlot;
}

Index

Properties

assurancesAvailAssignment guarantees newEntropy offenders recentBlocksPartialUpdate slot

Properties

assurancesAvailAssignment

assurancesAvailAssignment: AssurancesStateUpdate["availabilityAssignment"]

ρ‡ - Availability assignment resulting from assurances transition https://graypaper.fluffylabs.dev/#/1c979cb/141302144402?v=0.7.1

guarantees

guarantees: GuaranteesExtrinsicView

A work-package, is transformed by validators acting as guarantors into its corresponding work-report, which similarly comprises several work outputs and then presented on-chain within the guarantees extrinsic.

https://graypaper.fluffylabs.dev/#/5f542d7/133500133900