Move EIP-1283 status to last call

[sorpaas]

The spec is finalized, covered with test cases, and had an informal proof. See discussion on ethereum/pm#55

[eip-automerger]

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

• Trying to change EIP 1283 state from Draft to Accepted

[axic]

@gumb0 @holiman @5chdn I am not sure what the process is regarding moving this from Draft to Accepted, but I think it is mostly down to the client implementers doing the hard fork changes.

[5chdn]

It's accepted as decided in the constantinople session 1, see also meta eip, e.g., #1366

[axic]

Actually it seems according to the EIP-1 this should go through a Last Call step first:

Accepted (Core EIPs only) -- A successful Last Call without material changes or unaddressed technical complaints will become Accepted.

[sorpaas]

@axic That looks like a new change in the EIP process after I made this PR -- I don't remember previously Core EIPs had "Last Call" status. (Edit: the change #1224 was earlier, my fault!)

Anyway, just changed!

[axic]

@sorpaas also it seems that the Last Call would require an additional field: review-period-end:

Though perhaps for hard fork related EIPs the last call process is not enforced.