pub enum CollateralBufferUnknownReason {
RequirementUnknown,
ServedSetUnknown,
ReclaimStateUnknown,
BalanceUnknown,
}Expand description
Why a node cannot state its recommended buffer or its funding position.
Separate from CollateralUnknownReason because the buffer needs three facts the epoch
requirement does not, and each has a different remedy: a node missing its served set needs its
hosted-store view, one missing reclaim state needs its transition bookkeeping, and one missing
its balance needs a chain source. Collapsing them into the requirement’s reasons would answer
every one of those with “not censused”, which is both false and unactionable.
Variants§
RequirementUnknown
The epoch requirement itself is unknown, so every term scaled by it is unknown too. Call
control.collateral.requirement for WHICH fact is missing — this variant deliberately does
not restate that taxonomy, because a copy of it here would drift from the original.
ServedSetUnknown
The node cannot enumerate the (owner, store, root) pairs IT serves. Nothing may be
substituted for this: the census stores figure counts network-wide advertisements and is
not a count of this node’s own set.
ReclaimStateUnknown
The node cannot read how much collateral is still locked against positions it has not yet reclaimed, so the transition-overlap term is unknown.
BalanceUnknown
The node cannot read its own spendable $DIG, so it can state a buffer but not a position against it.
Implementations§
Trait Implementations§
Source§impl Clone for CollateralBufferUnknownReason
impl Clone for CollateralBufferUnknownReason
Source§fn clone(&self) -> CollateralBufferUnknownReason
fn clone(&self) -> CollateralBufferUnknownReason
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more