The relative stake of a stakepool in relation to the total amount staked. A value in the [0, 1] range.

The accumulated relative stake of a stake pool, like PoolStake but it also includes the relative stake of all preceding pools. A value in the range [0, 1].

A boolean like type. Big ledger peers are the largest SPOs which control 90% of staked stake.

Note that IsBigLedgerPeer indicates a role that peer plays in the eclipse evasion, e.g. that a peer was explicitly selected as a big ledger peer, e.g. IsNotBigLedgerPeer does not necessarily mean that the peer isn't a big ledger peer. This is because we select root peers from all ledger peers (including big ones).

Wether the node is caught up or fell too far behind the chain

Return ledger state information and ledger peers.

Only use the ledger after the given slot number.

Only use the ledger after the given slot number.

Which ledger peers to pick.

The type of big ledger peers that is serialised or later provided by node configuration for the networking layer to connect to when syncing.

Minimum number of hot big ledger peers in Genesis mode for trusted state to be signalled to Consensus. This number should be smaller than the targetNumberOfActiveBigLedgerPeers but greater than 1. In Genesis, we may demote a big ledger peer for underperformance, but not promote a replacement immediately to guard against adversaries which may want to slow down our progress.

Since ledger peer snapshot is serialised with all domain names fully qualified, and all stake values are approximate in floating point, comparison is necessarily approximate as well. The candidate argument is processed here to simulate a round trip by the serialisation mechanism and then compared to the baseline argument, which is assumed that it was actually processed this way when a snapshot was created earlier, and hence it is approximate as well. The two approximate values should be equal if they were created from the same faithful data.