ϑ theta: We also maintain knowledge of ready (i.e. available
and/or audited) but not-yet-accumulated work-reports in
the state item ϑ.
α alpha: Authorizers available for each core (authorizer pool).
φ phi: A queue of authorizers for each core used to fill up the pool.
Only updated by accumulate calls using assign host call.
ρ rho: work-reports which have been reported but are not yet known to be
available to a super-majority of validators, together with the time
at which each was reported.
κ kappa: Validators, who are the set of economic actors uniquely
privileged to help build and maintain the Jam chain, are
identified within κ, archived in λ and enqueued from ι.
ι iota: The validator keys and metadata to be drawn from next.
Retrieve details about single service.
λ lambda: Validators, who are the set of economic actors uniquely
privileged to help build and maintain the Jam chain, are
identified within κ, archived in λ and enqueued from ι.
β beta: State of the blocks from recent history.
ξ xi: In order to know which work-packages have been
accumulated already, we maintain a history of what has
been accumulated. This history, ξ, is sufficiently large
for an epoch worth of work-reports.
π pi: Previous and current statistics of each validator,
cores statistics and services statistics.
https://graypaper.fluffylabs.dev/#/68eaa1f/18f60118f601?v=0.6.4
A non-decoding version of the
State.Note we don't require all fields to have view accessors, since it's only beneficial for large collections to be read via views.
https://graypaper.fluffylabs.dev/#/579bd12/08f10008f100