mirror of
https://github.com/pezkuwichain/consensus.git
synced 2026-06-19 22:51:01 +00:00
Unstaged changes but commiting to save from CR/LF mess
This commit is contained in:
@@ -183,6 +183,8 @@ fishermen, which sounds problematic.
|
|||||||
# Timing
|
# Timing
|
||||||
|
|
||||||
TODO: Comment on relative block time vs. more absolute synced clock times.
|
TODO: Comment on relative block time vs. more absolute synced clock times.
|
||||||
|
ability to have timeout that depend on network activity? (relative absolute time??)
|
||||||
|
but think about the network conditions
|
||||||
|
|
||||||
We seemingly need a bound on clock skew between validators, which
|
We seemingly need a bound on clock skew between validators, which
|
||||||
we must enforce using the peer-to-peer network.
|
we must enforce using the peer-to-peer network.
|
||||||
@@ -202,3 +204,10 @@ slower than the overall network, but as their stake increases this
|
|||||||
rate goes up. Ouroboros wants to prevent this initial slow start,
|
rate goes up. Ouroboros wants to prevent this initial slow start,
|
||||||
but this requires
|
but this requires
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### Ideas
|
||||||
|
|
||||||
|
Unavailability game
|
||||||
|
Time or relative time signing
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user