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

5 ETH phase 0 bounties #1345

Open
JustinDrake opened this issue Aug 7, 2019 · 5 comments

Comments

@JustinDrake
Copy link
Collaborator

commented Aug 7, 2019

  • Prize—5 ETH (or 1000 DAI, whichever largest) for any substantive change to the master branch merged prior to the Eth2 genesis. Security fixes may be rewarded more at the discretion of the research team.
  • Scope—Substantive changes to the phase 0 spec for either:
    • state transition functionhash_tree_root(state_transition(state, block)) changes for some inputs state and block, or
    • fork choice ruleget_head(store) changes after some received sequence of blocks and attestations at specific times, or
    • deposit contract—changes to the contract bytecode
  • Exclusions—The following are out of scope:
  • Participate—To participate open an issue or PR with a description of the issue or suggested change. After the substantive change is merged into master ask @JustinDrake for payment.
@vbuterin

This comment has been minimized.

Copy link
Contributor

commented Aug 7, 2019

Scope—Substantive changes to the phase 0 state transition function, i.e. changes that modify hash_tree_root(state_transition(state, block)) for some inputs state and block.

And the fork choice rule?

@JustinDrake

This comment has been minimized.

Copy link
Collaborator Author

commented Aug 7, 2019

And the fork choice rule?

Added :)

@JustinDrake JustinDrake changed the title (proposal) 5 ETH phase 0 bounties 5 ETH phase 0 bounties Aug 15, 2019

@ethers

This comment has been minimized.

Copy link
Member

commented Aug 29, 2019

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?

@djrtwo

This comment has been minimized.

Copy link
Contributor

commented Aug 29, 2019

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

@ethers

This comment has been minimized.

Copy link
Member

commented Aug 29, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.