OptionalamendmentsThe value validationReceived indicates this is from the validations Stream.
Optionalbase_The amendments this server wants to be added to the protocol.
OptionalcookieAn arbitrary value chosen by the server at startup.
If the same validation key pair signs validations with different cookies concurrently, that usually indicates that multiple servers are incorrectly configured to use the same validation key pair.
OptionaldataThe contents of the validation message in its canonical binary form
The unscaled transaction cost (reference_fee value) this server wants to set by Fee voting.
Bit-mask of flags added to this validation message. The flag 0x80000000 indicates that the validation signature is fully-canonical. The flag 0x00000001 indicates that this is a full validation; otherwise it's a partial validation. Partial validations are not meant to vote for any particular ledger. A partial validation indicates that the validator is still online but not keeping up with consensus.
If true, this is a full validation. Otherwise, this is a partial validation. Partial validations are not meant to vote for any particular ledger. A partial validation indicates that the validator is still online but not keeping up with consensus.
The ledger index of the proposed ledger.
Optionalload_The local load-scaled transaction cost this validator is currently enforcing, in fee units.
Optionalmaster_The validator's master public key, if the validator is using a validator token, in the XRP Ledger's base58 format.
Optionalnetwork_The network from which the validations stream is received.
Optionalreserve_The minimum reserve requirement (account_reserve value) this validator
wants to set by fee voting.
Optionalreserve_The increment in the reserve requirement (owner_reserve value) this validator wants to set by fee voting.
The signature that the validator used to sign its vote for this ledger.
When this validation vote was signed, in seconds since the Ripple Epoch.
The public key from the key-pair that the validator used to sign the message, in the XRP Ledger's base58 format. This identifies the validator sending the message and can also be used to verify the signature. If the validator is using a token, this is an ephemeral public key.
The validations stream sends messages whenever it receives validation messages, also called validation votes, regardless of whether or not the validation message is from a trusted validator.