Timeline for How do Ethereum clients cope with future blocks?
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 15, 2018 at 11:19 | history | edited | Константин Ван | CC BY-SA 4.0 |
Fixed grammar
|
Oct 31, 2017 at 9:33 | history | edited | Константин Ван | CC BY-SA 3.0 |
added 17 characters in body
|
Oct 3, 2017 at 16:10 | vote | accept | Константин Ван | ||
Oct 2, 2017 at 13:40 | comment | added | Константин Ван | @EdmundEdgar Done. They update the timestamp of the block they're mining to be 1 second later than the future block they just accepted. Geth waits (sleeps) for some seconds not to mine future blocks, whereas Parity doesn't. :) | |
Oct 2, 2017 at 4:44 | comment | added | Константин Ван | @EdmundEdgar Good catch. Now I'm reading the source code of Parity and Geth about what you said. I'll comment as my investigation gets done. | |
Oct 2, 2017 at 1:50 | comment | added | Edmund Edgar | Out of interest, if Geth and Parity get a block with a timestamp 29 seconds in the future, do they update the timestamp of the block they're mining to be later than the one they just accepted, or do they just keep trying to mine a block that, if successful, they would consider invalid because the timestamp goes backwards? | |
Oct 1, 2017 at 13:54 | history | answered | Константин Ван | CC BY-SA 3.0 |