mirror of
https://github.com/Xahau/xahaud.git
synced 2026-07-25 16:10:15 +00:00
c92c0656ec
Replace the zero-entropy fallback with a deterministic consensus-bound digest so every RNG-enabled ledger carries usable entropy: - sha512Half(HashPrefix::entropyFallback, prevLedgerHash, baseTxSetHash, seq) — all inputs are already consensus-agreed at injection time, so no new agreement machinery is needed and the digest is identical on every node building the same ledger - new sfEntropyTier (UINT8) on the ttCONSENSUS_ENTROPY pseudo-tx and ConsensusEntropy ledger entry: EntropyCount says how many validators contributed, EntropyTier says which gate the result passed (validator_quorum vs consensus_fallback; participant_aligned reserved) - the fallback digest derives from the BASE (pre-injection) tx set hash to avoid circularity; entropy pseudo-tx dedup is now type-based since an explicit-final synthetic set can carry a pseudo-tx whose txID implicit nodes cannot re-derive - unparseable-entropy-set residual now falls back instead of skipping injection, so a fresh ConsensusEntropy entry exists every ledger - CSF Peer mirrors the fallback analog; sims assert deterministic non-zero fallback digests across same-LCL peers - testnet scenarios updated: degraded windows expect labeled fallback entropy, never validator-tier The fallback tier is user-influenceable via tx submission (quiet-ledger grinding) and is labeled accordingly — hook-facing gating lands with the min_tier/min_count API change.
protocol
Classes and functions for handling data and values associated with the XRP Ledger protocol.
Serialized Objects
Objects transmitted over the network must be serialized into a canonical format. The prefix "ST" refers to classes that deal with the serialized format.
The term "Tx" or "tx" is an abbreviation for "Transaction", a commonly occurring object type.
Optional Fields
Our serialized fields have some "type magic" to make optional fields easier to read:
- The operation
x[sfFoo]means "return the value of 'Foo' if it exists, or the default value if it doesn't." - The operation
x[~sfFoo]means "return the value of 'Foo' if it exists, or nothing if it doesn't." This usage of the tilde/bitwise NOT operator is not standard outside of therippledcodebase.- As a consequence of this,
x[~sfFoo] = y[~sfFoo]assigns the value of Foo from y to x, including omitting Foo from x if it doesn't exist in y.
- As a consequence of this,
Typically, for things that are guaranteed to exist, you use
x[sfFoo] and avoid having to deal with a container that may
or may not hold a value. For things not guaranteed to exist,
you use x[~sfFoo] because you want such a container. It
avoids having to look something up twice, once just to see if
it exists and a second time to get/set its value.
(Real example)
The source of this "type magic" is in SField.h.