ethereum/go-ethereum

Istanbul hard-fork meta

karalabe opened this issue · 4 comments

Accepted EIPs:

Maintenance stuff:

  • Define the Istanbul fork chain config (#19904)
  • Integrate Istanbul meta fork config with individual EIPs (#19993)
  • Define --istanbul.override flag to support last minute delay (#20004)
  • Integrate Istanbul into Puppeth
    • #19926 - need the chain specs for Parity, need to finalize everything before letting people enable it

Re blake, see keep-network#4

The implementation for calldata EIP can be found liorgold2#1

Re "sane limits"

As far as I see it based on the discussions in https://ethereum-magicians.org/t/eip-1985-sane-limits-for-certain-evm-parameters/3224, all the proposed "limits" are already practical invariants of the system. I'm not sure what this EIP is supposed to "do" in Istanbul.

The only thing that actually makes a difference, is that it would make the following invalid:

  • A block which has an uncle, where the uncle.timestamp does not fit within int32.

We need to coordinate on that change, otherwise there's a window of attackability by malicious miner. If we do that, and nobody "exploits" until then (which would be meaningless), then we can later post-facto declare "It has always been thus".

I think this can be closed now, as istanbul is long merged