Module hotshot_types::constants
source · Expand description
configurable constants for hotshot
Constants§
- timeout for fetching auction results from the solver
- timeout for fetching bundles from builders
- the number of messages to cache in the combined network
- the default delay duration value in milliseconds of sending on the secondary in the combined networks
- the number of messages to attempt to send over the primary network before switching to prefer the secondary network
- the number of messages to send over the secondary network without delay before re-attempting the (presumed down) primary network
- Default channel size for consensus event sharing
- Default channel size for HotShot -> application communication
- the default kademlia record republication interval (in seconds)
- The
tide
module name for the legacy builder - the number of views to gather information for ahead of time
- The
tide
module name for the marketplace builder - default number of rounds to run
- default number of transactions per round
- default size of transactions
- The default network data request delay in milliseconds
- For
STAKE_TABLE_CAPACITY=200
, the light client prover (a.k.a.hotshot-state-prover
) would need to generate proof for a circuit of slightly below 2^20 gates. Thus we need to support this upperbounded degree in our Structured Reference String (SRS), the+2
is just an artifact from the jellyfish’s Plonk proof system. - The offset for how far in the future the upgrade actually begins.
- The offset for how far in the future the upgrade certificate we attach should be decided on (or else discarded).
- The offset for how far in the future the upgrade ends.
- The offset for how far in the future we will send out a
QuorumProposal
with anUpgradeCertificate
we form. This is also how far in advance of sending aQuorumProposal
we begin collecting votes on anUpgradeProposal
.