You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ChainDB only processes blocks it set aside as future blocks the next time a block is added. From the report:
In a way, calls to addBlock are how the chain database sees time advance.
Suppose we receive a block B that is slightly in the future, then idle long enough for B to no longer be in the future, and then forge a new block. Since we didn't receive any blocks after idling, we will not forge on top of B.
Since leadership opportunities are precious, we wouldn't want to squander one like that: forging on top of B would have made a more competitive block.
The text was updated successfully, but these errors were encountered:
The ChainDB only processes blocks it set aside as future blocks the next time a block is added. From the report:
Suppose we receive a block B that is slightly in the future, then idle long enough for B to no longer be in the future, and then forge a new block. Since we didn't receive any blocks after idling, we will not forge on top of B.
Since leadership opportunities are precious, we wouldn't want to squander one like that: forging on top of B would have made a more competitive block.
The text was updated successfully, but these errors were encountered: