-
Notifications
You must be signed in to change notification settings - Fork 6
core/block_validator.go#calcDifficultyAtlantis is wrong #67
Comments
Only EIP100 should be introduced. |
yeah adding the bomb delay segment was because I wasn't aware ETC defused the difficulty bomb when adding that in (ETC has an equivalent of the EIPs you mentioned) and I wanted to make sure the client stayed in sync with other clients (as other clients had this value in) Very minor change as it doesn't affect anything really but I'll have a PR in soon |
At block 11,500,000 (or fork number + 3000000) the network would have forked if this client were in play. Block difficulty is a consensus issue. Although yes, the fix is simple. |
Yeah another case of not choosing my words carefully, I meant to say it wasn't an urgent PR since those blocks are so |
where **~ 486 days**
is more like "the next few decades", eg. |
May we please revert back to testing and less on semantics. Thank you for identifying the bug, we're working on it 😄 |
Done #69 |
https://github.com/eth-classic/go-ethereum/blob/development/core/block_validator.go#L362
At first review this appears to use a hardcoded bomb delay value according to EIP1234, which is not relevant to ETC nor Atlantis.
Atlantis occurs canonically after ECIP1010 (difficulty bomb defuse), which makes this spec and logic inapplicable.
The text was updated successfully, but these errors were encountered: