Updating EIP 2515 for clarity.

[MadeofTin]

When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md

We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met:

• The PR edits only existing draft PRs.
• The build passes.
• Your GitHub username or email address is listed in the 'author' header of all affected PRs, inside .
• If matching on email address, the email address is the one publicly listed on your GitHub profile.

[eip-automerger]

Hi! I'm a bot, and I wanted to automerge your PR, but couldn't because of the following issue(s):

• EIP header in EIPS/eip-2515.md does not match: 2512

[axic]

How was this merged with the wrong number in the first place?

[MadeofTin]

No idea. It confuses me.

[axic]

All these fields are broken:

created: 2020/02/10
requires (*optional):
replaces (*optional):

[axic]

Suggested change

	created: 2020/02/10
	created: 2020-02-10

[axic]

There is a single difficulty bomb:

Suggested change

The current difficulty bombs' effect on the Block Time Targeting mechanism is rather complex to model, and it has both appeared when it was not expected (Muir Glacier) and negatively affected users and miners when they are not the target (in the case of delaying forks due to technical difficulties). Users are affected as a function of the usability of the chain is affected by increased block times. Miners are affected by a reduction in block rewards due to the increase in block time. Both of these groups are unable on their own to address the difficulty bomb. In the case of the Difficulty Freeze it is more predictiable and so knowing when to make the change is readily apparent at all times.

The current difficulty bomb's effect on the Block Time Targeting mechanism is rather complex to model, and it has both appeared when it was not expected (Muir Glacier) and negatively affected users and miners when they are not the target (in the case of delaying forks due to technical difficulties). Users are affected as a function of the usability of the chain is affected by increased block times. Miners are affected by a reduction in block rewards due to the increase in block time. Both of these groups are unable on their own to address the difficulty bomb. In the case of the Difficulty Freeze it is more predictable and so knowing when to make the change is readily apparent at all times.

[axic]

@MadeofTin you need to click the "Resolve conflicts" button and manually fix the issues, otherwise this can not be merged:

[lightclient]

Pinging @MadeofTin.

[github-actions]

There has been no activity on this pull request for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.

[github-actions]

This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.