Module massa_models::config::constants
source · Expand description
DEFAULT VALUES USED TO INITIALIZE DIVERS CONFIGURATIONS STRUCTURES
Default hard-coded
Each crates may contains a settings.rs or a config.rs the Default
implementation of each object take the default Values from the following
file.
These values are the hard-coded values that make sens to never be modified
by a user. Generally, this values are passed with dependency injection in a cfg
parameter for each worker, that is convenient for unit tests.
A parallel file with the same constant definitions exist for the testing case.
(default_testing.rs) But as for the current file you shouldn’t modify it.
Structs
- node chain id (to avoid replay attacks)
- TESTNET: time when the blockclique is ended.
KeyPairto sign genesis blocks.- Time in milliseconds when the blockclique started. In sandbox mode, the value depends on starting time and on the –restart-from-snapshot-at-period argument in CLI, so that the network starts or restarts 10 seconds after launch
- number of cycle misses (strictly) above which stakers are deactivated
- node version
Constants
- Constant cost applied to asynchronous messages (to take into account some costs related to snapshot)
- Gas used by a base operation (transaction, roll buy, roll sell)
- Block reward is given for each block creation
- Size of the random bytes array used for the bootstrap, safe to import
- Consensus static parameters (defined by protocol used) Changing one of the following values is considered as a breaking change Values differ in
testflavor building for faster CI and simpler scenarios - Maximum number of consensus blocks in a bootstrap batch
- max change denominator
- deferred call call gas cost
- deferred call global overbooking penalty
- maximum gas for deferred call
- Maximum size of deferred call future slots (1 week)
- Maximum size of deferred call pool changes
- deferred call max gas cost (10 nanomassa)
- deferred call min gas increment (1 nanomassa)
- deferred call slot overbooking penalty
- Threshold for fitness.
- denunciation expiration delta
- Number of endorsement
- Length of the handshake random signature
- Proof of stake seed for the initial draw
- Max size of the IP list
- Number of periods of executed operation and denunciation history to keep
- Cost to store one byte in the ledger
- Cost for a base entry default 0.01 MASSA
- Base size of a empty datastore entry (not counting the key nor the value)
- Limit on the number of peers we advertise to others.
- Maximum of GAS allowed for asynchronous messages execution on one slot
- Maximum capacity of the asynchronous messages pool
- Maximum block size in bytes
- Max async pool changes
- Max number of blocks we provide/ take into account while bootstrapping
- Max number of child nodes
- max bootstrapped cliques
- max bootstrapped dependencies
- Max size of the printed error
- Max bytes in final states parts
- Max message size for bootstrap Note: Update sizes are not limited, the 190Mb constant is to take them into account.
- The number of bytes needed to encode
MAX_BOOTSTRAP_MESSAGE_SIZE - Max number of cycles in PoS bootstrap
- Max bytes in final states parts
- Maximum length of a datastore value
- Maximum number of consensus block ids when sending a bootstrap cursor from the client
- Maximum number of key/values in the datastore of a ledger entry
- Maximum length of a datastore key
- Maximum length of a datastore value
- Maximum size proof-of-stake deferred credits
- Max number of denunciations that can be included in a block header
- Maximum size of executed denunciations
- max duplex buffer size
- Max number of endorsements per message
- Maximum event size in bytes
- Maximum size of executed ops changes
- Maximum size of executed ops
- Maximum length function name in call SC
- Maximum of GAS allowed for a block
- Maximum ledger changes count
- Maximum ledger changes in a block
- Maximum number of listeners for a peer
- Maximum message length in bytes
- Maximum number of operations per block
- Max number of operations per message
- Maximum number of key/values in the datastore of a
ExecuteSCoperation - Maximum length of an operation datastore key
- Maximum length of an operation datastore value
- Maximum of time we keep the operations in the storage of the propagation thread
- Maximum size of parameters in call SC
- Maximum number of peer in a announcement list of peer
- Maximum production events in a block
- Maximum size of proof-of-stake production stats
- Maximum length of
rng_seedin thread cycle - Maximum size of proof-of-stake rolls
- Maximum size of channel used for commands in connectivity thread
- Maximum size of channel used for commands in peers management thread
- Maximum size of channel used for commands in peer testers thread
- Maximum size of channel used for commands in propagation thread of block
- Maximum size of channel used for commands in propagation thread of endorsements
- Maximum size of channel used for commands in propagation thread of operations
- Maximum size of channel used for commands in retrieval thread of block
- Maximum size of channel used for commands in retrieval thread of endorsements
- Maximum size of channel used for commands in retrieval thread of operations
- Maximum size of channel used to send network events to the block handler
- Maximum size of channel used to send network events to the endorsement handler
- Maximum size of channel used to send network events to the operation handler
- Maximum size of channel used to send network events to the peer handler
- Block count to process in MipStoreStats (for state change threshold)
- network controller communication channel size
- network event channel size
- network node command channel size
- network node event channel size
- node send channel size
- Maximum operation validity period count
- cycle duration in periods
- Pool controller denunciations channel size
- Pool controller endorsements channel size
- Pool controller operations channel size
- Number of cycles saved in
PoSFinalState - Protocol controller channel size
- Protocol event channel size
- Number of roll to remove per denunciation
- Price of a roll in the network
- Number of cycle draws saved in the selector cache
- IMPORTANNT TODO: should be removed after the bootstrap messages refacto
- Time between the periods in the same thread.
- Number of threads
- Minimum value allowed for activation delay (in MIP info)
- Threshold to accept a new versioning
Functions
- Helper function to parse args for lazy_static evaluations