-
Notifications
You must be signed in to change notification settings - Fork 997
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
5 ETH phase 0 bounties #1345
Comments
And the fork choice rule? |
Added :) |
Although a known open issue, should #1303 be eligible? Are there any other open issues that could use more help and where substantive feedback/changes could be rewarded? |
This bounty is specifically for identifying bugs and other substantive changes that should be made to the phase 0 related specs prior to mainnet launch. Anything identified in an existing issue is not eligible for this bounty |
Got it this is strictly phase0. To the extent that bounties are helpful, maybe a separate bounty should be considered for open issues that could use more help or substantive feedback... Kind of a difference between asking people to review something at the "end", vs encouraging (more) participation during the process. A bounty could help signal areas where more attention is desired. |
Note! This program is suspended until we make the next couple of releases. It will be re-instituted in mid-January |
Closing this issue. We are reformulating the program and will release details asap |
The current Bounty Program is at per https://blog.ethereum.org/2020/03/31/eth2-quick-update-no-10/ |
master
branch merged prior to the Eth2 genesis. Security fixes may be rewarded more at the discretion of the research team.hash_tree_root(state_transition(state, block))
changes for some inputsstate
andblock
, orget_head(store)
changes after some received sequence ofblock
s andattestation
s at specifictime
s, ormaster
ask @JustinDrake for payment.The text was updated successfully, but these errors were encountered: