diff options
| author | Anthony Towns <aj@erisian.com.au> | 2020-10-17 17:24:10 +1000 |
|---|---|---|
| committer | Anthony Towns <aj@erisian.com.au> | 2020-10-17 17:24:15 +1000 |
| commit | b6b5b923374299ac1535f90749b879b7dc39883f (patch) | |
| tree | 9000b9e5f50b39d2234af5827c4eef928313b84c /bip-0098/skip-skip.png | |
| parent | 0f683f71f58f05d314cf943700558a82aba63102 (diff) | |
BIP8: clarify timeoutheight behaviour and requirements
When lockinontimeout is true, we don't transition directly from STARTED
to LOCKED_IN, so don't imply that we do.
If startheight or timeoutheight are not on a retarget boundary, they
behave as if they had been rounded up to the next retarget boundary,
so to keep things simple, require them to be at a boundary.
If timeoutheight is less than two retarget periods later than startheight,
behaviour when lockinontimeout is true (one retarget period of STARTED,
one of MUST_SIGNAL, one of LOCKED_IN, then ACTIVE) will not match
behaviour when lockinontimeout is false (one retarget period of STARTED,
then either LOCKED_IN or FAILED), so disallow that as well.
Diffstat (limited to 'bip-0098/skip-skip.png')
0 files changed, 0 insertions, 0 deletions