Warp timestamp and extend max-allowable-drift for accommodate slow blocks (#15204)
* Remove timestamp_correction feature gating * Remove timestamp_bounding feature gating * Remove unused deprecated ledger code * Remove unused deprecated unbounded-timestamp code * Enable independent adjustment of fast/slow timestamp bounding * Update timestamp bounds to 25% fast, 80% slow; warp timestamp * Update bank hash test * Add PR number to feature Co-authored-by: Michael Vines <mvines@gmail.com> Co-authored-by: Michael Vines <mvines@gmail.com>
This commit is contained in:
@ -387,11 +387,6 @@ intermittently adding a timestamp to a Vote for a particular block. A requested
|
||||
block's time is calculated from the stake-weighted mean of the Vote timestamps
|
||||
in a set of recent blocks recorded on the ledger.
|
||||
|
||||
Nodes that are booting from snapshot or limiting ledger size (by purging old
|
||||
slots) will return null timestamps for blocks below their lowest root +
|
||||
`TIMESTAMP_SLOT_RANGE`. Users interested in having this historical data must
|
||||
query a node that is built from genesis and retains the entire ledger.
|
||||
|
||||
#### Parameters:
|
||||
|
||||
- `<u64>` - block, identified by Slot
|
||||
|
Reference in New Issue
Block a user