-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[bounty] Missing ~Byzantium~ EIPS #2221
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 1.188 ETH (251.1 USD @ $211.36/ETH) attached to it as part of the ChainSafe Systems fund.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of this issue was increased to 1.189 ETH (252.23 USD @ $212.14/ETH) (plus a crowdfund of 1.118 ETH worth 237.17141298435 USD).
|
shouldn't limit this to byzantium IMO |
Yeah, valid - let's open it up @decanus |
Closing because Atlantis succeeded |
Issue Status: 1. Open 2. Cancelled The funding of 1.189 ETH (plus a crowdfund of 1.1280000000000001 ETH worth 233.70647417424001 USD) (246.34 USD @ $207.19/ETH) attached to this issue has been cancelled by the bounty submitter
|
EDIT: We have extended this to ANY already implemented hard fork.
In light of #2220 myself and @decanus are opening up a $500 bounty to whomever discovers missing EIPS or consensus breaking changes in
Byzantium, meta issue here.ANY already implemented hard fork. Meta issues can be found in the EIPs repository.The deadline for this will be September (because of an upcoming ETC hardfork) and we're happy to extend this to find ANY other discrepancies to ensure our meta hardfork EIPS are correctly documented!The deadline will be on 2019-10-15, the eve of the Istanbul hard fork (2019-10-16). Once, completed, the payout will be equally based on how many discrepancies were found (1/5 discrepancies, 1/5 of the reward...).
NOTE: #2220 does not count
The text was updated successfully, but these errors were encountered: