Timing parameters to control validation staleness and expiration. More...

Collaboration diagram for ripple::ValidationParms:

Public Member Functions
	ValidationParms ()=default

Public Attributes
std::chrono::seconds	validationCURRENT_WALL = std::chrono::minutes{5}
	The number of seconds a validation remains current after its ledger's close time. More...

std::chrono::seconds	validationCURRENT_LOCAL = std::chrono::minutes{3}
	Duration a validation remains current after first observed. More...

std::chrono::seconds	validationCURRENT_EARLY = std::chrono::minutes{3}
	Duration pre-close in which validations are acceptable. More...

std::chrono::seconds	validationSET_EXPIRES = std::chrono::minutes{10}
	Duration a set of validations for a given ledger hash remain valid. More...

std::chrono::seconds	validationFRESHNESS = std::chrono::seconds{20}
	How long we consider a validation fresh. More...

Detailed Description

Timing parameters to control validation staleness and expiration.

Note: These are protocol level parameters that should not be changed without careful consideration. They are not implemented as static constexpr to allow simulation code to test alternate parameter settings.

Definition at line 45 of file Validations.h.

Constructor & Destructor Documentation

◆ ValidationParms()

ripple::ValidationParms::ValidationParms ( )

explicitdefault

Member Data Documentation

◆ validationCURRENT_WALL

std::chrono::seconds ripple::ValidationParms::validationCURRENT_WALL = std::chrono::minutes{5}

The number of seconds a validation remains current after its ledger's close time.

This is a safety to protect against very old validations and the time it takes to adjust the close time accuracy window.

Definition at line 55 of file Validations.h.

◆ validationCURRENT_LOCAL

std::chrono::seconds ripple::ValidationParms::validationCURRENT_LOCAL = std::chrono::minutes{3}

Duration a validation remains current after first observed.

The number of seconds a validation remains current after the time we first saw it. This provides faster recovery in very rare cases where the number of validations produced by the network is lower than normal

Definition at line 63 of file Validations.h.

◆ validationCURRENT_EARLY

std::chrono::seconds ripple::ValidationParms::validationCURRENT_EARLY = std::chrono::minutes{3}

Duration pre-close in which validations are acceptable.

The number of seconds before a close time that we consider a validation acceptable. This protects against extreme clock errors

Definition at line 70 of file Validations.h.

◆ validationSET_EXPIRES

std::chrono::seconds ripple::ValidationParms::validationSET_EXPIRES = std::chrono::minutes{10}

Duration a set of validations for a given ledger hash remain valid.

The number of seconds before a set of validations for a given ledger hash can expire. This keeps validations for recent ledgers available for a reasonable interval.

Definition at line 78 of file Validations.h.

◆ validationFRESHNESS

std::chrono::seconds ripple::ValidationParms::validationFRESHNESS = std::chrono::seconds{20}

How long we consider a validation fresh.

The number of seconds since a validation has been seen for it to be considered to accurately represent a live proposer's most recent validation. This value should be sufficiently higher than ledgerMAX_CONSENSUS such that validators who are waiting for laggards are not considered offline.

Definition at line 88 of file Validations.h.

Public Member Functions

Public Attributes