Timeline for How does the Ethereum Homestead difficulty adjustment algorithm work?
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 21, 2018 at 19:38 | comment | added | Paul Razvan Berg | @greatwolf it's a difficulty bound divisor, had it been smaller, the incentives wouldn't work out | |
Jun 26, 2017 at 9:39 | comment | added | Piotr Dobrogost |
The ranges used in the summary do not contain (19,20) range.
|
|
Apr 13, 2017 at 13:01 | history | edited | CommunityBot |
replaced http://ethereum.stackexchange.com/ with https://ethereum.stackexchange.com/
|
|
Jan 25, 2017 at 15:45 | comment | added | hhh | @BokkyPooBah I love that you gave yourself the time to write this detailed account: I learned from it. I want to add the following: github.com/ethereum/go-ethereum/blob/… No matter how poor is your hashrate, there is a minimum you cannot go under. github.com/ethereum/go-ethereum/blob/… | |
Aug 7, 2016 at 23:18 | comment | added | greatwolf |
Okay this makes sense, essentially you're looking at the timestamp difference from the last 2 blocks and you're extracting the 2nd significant digit. That digit is the determining factor whether blocks are too slow, too fast or just right. Can you explain the 2048 magic number though? What's the idea behind dividing it by 2048 and why that number?
|
|
Jul 13, 2016 at 15:52 | history | edited | BokkyPooBah | CC BY-SA 3.0 |
Updated typos as corrected by @varm
|
Jul 13, 2016 at 15:44 | comment | added | galahad |
@BookyPooBah Thanks for a detailed walk-through. In your explanation for subformula A and A1, for 20-29 seconds and 30-39 seconds, isn't the result of A1 -1 and -2 respectively?
|
|
Jun 14, 2016 at 11:16 | vote | accept | BokkyPooBah | ||
Jun 11, 2016 at 15:55 | history | edited | BokkyPooBah | CC BY-SA 3.0 |
Added source code
|
Jun 11, 2016 at 15:42 | history | edited | BokkyPooBah | CC BY-SA 3.0 |
Tidy
|
Jun 11, 2016 at 15:36 | history | answered | BokkyPooBah | CC BY-SA 3.0 |