Warn lastValidSlot with some terminology tweaks (#15081)
* Warn lastValidSlot with some terminology tweaks * Apply suggestions from code review Co-authored-by: Tyera Eulberg <teulberg@gmail.com> * Restore previous arrangment of slot def. and tweak upon it * Apply suggestions from code review Co-authored-by: Tyera Eulberg <teulberg@gmail.com> Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
This commit is contained in:
@@ -136,7 +136,7 @@ The role of a [validator](terminology.md#validator) when it is appending [entrie
|
||||
|
||||
## leader schedule
|
||||
|
||||
A sequence of [validator](terminology.md#validator) [public keys](terminology.md#public-key). The cluster uses the leader schedule to determine which validator is the [leader](terminology.md#leader) at any moment in time.
|
||||
A sequence of [validator](terminology.md#validator) [public keys](terminology.md#public-key) mapped to [slots](terminology.md#slot). The cluster uses the leader schedule to determine which validator is the [leader](terminology.md#leader) at any moment in time.
|
||||
|
||||
## ledger
|
||||
|
||||
@@ -217,9 +217,17 @@ A 64-byte ed25519 signature of R (32-bytes) and S (32-bytes). With the requireme
|
||||
This requirement ensures no signature malleability. Each transaction must have at least one signature for [fee account](terminology#fee-account).
|
||||
Thus, the first signature in transaction can be treated as [transacton id](terminology.md#transaction-id)
|
||||
|
||||
## skipped slot
|
||||
|
||||
A past [slot](terminology.md#slot) that did not produce a [block](terminology.md#block), because the leader was offline or the [fork](terminology.md#fork) containing the slot was abandoned for a better alternative by cluster consensus. A skipped slot will not appear as an ancestor for blocks at subsequent slots, nor increment the [block height](terminology#block-height), nor expire the oldest `recent_blockhash`.
|
||||
|
||||
Whether a slot has been skipped can only be determined when it becomes older than the latest [rooted](terminology.md#root) (thus not-skipped) slot.
|
||||
|
||||
## slot
|
||||
|
||||
The period of time for which a [leader](terminology.md#leader) ingests transactions and produces a [block](terminology.md#block).
|
||||
The period of time for which each [leader](terminology.md#leader) ingests transactions and produces a [block](terminology.md#block).
|
||||
|
||||
Collectively, slots create a logical clock. Slots are ordered sequentially and non-overlapping, comprising roughly equal real-world time as per [PoH](terminology.md#proof-of-history).
|
||||
|
||||
## smart contract
|
||||
|
||||
|
Reference in New Issue
Block a user