Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Istanbul hard-fork meta #19919

Closed
9 of 10 tasks
karalabe opened this issue Aug 6, 2019 · 4 comments
Closed
9 of 10 tasks

Istanbul hard-fork meta #19919

karalabe opened this issue Aug 6, 2019 · 4 comments

Comments

@karalabe
Copy link
Member

karalabe commented Aug 6, 2019

Accepted EIPs:

Maintenance stuff:

@holiman
Copy link
Contributor

holiman commented Aug 6, 2019

Re blake, see keep-network#4

@rjl493456442
Copy link
Member

The implementation for calldata EIP can be found liorgold2#1

@holiman
Copy link
Contributor

holiman commented Aug 12, 2019

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".

@karalabe karalabe changed the title Istanbul meta Istanbul hard-fork meta Aug 22, 2019
@MariusVanDerWijden
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants