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

Tracking: v0.0.1 milestone #411

Closed
paulhauner opened this issue Jun 25, 2019 · 2 comments
Closed

Tracking: v0.0.1 milestone #411

paulhauner opened this issue Jun 25, 2019 · 2 comments

Comments

@paulhauner
Copy link
Member

@paulhauner paulhauner commented Jun 25, 2019

Description

This issue should track the features we want to include/exclude from the v0.0.1 release milestone.

Tentative date: 15/7/19

Required Features:

  • A phase 0 testnet that can run on 1s slot times for 2 days.
  • VC/BN communications via HTTP.
  • A HTTP API beyond that of the minimal validator requirements.
  • Should not bypass any significant part consensus (except deposit contract).
  • Discovery via libp2p-discv5
  • Eth2-RPC re-write (Request/Responses via substreams rather than byte prefix)

Excluded Features:

  • Full deposit contract functionality.
  • Slashing detection or protection.

Info

Deposit contract is excluded as significant changes are expected to be introduced around spec-freeze (raised by J.Drake in an Eth2 call).

@paulhauner paulhauner added this to the v0.0.1 milestone Jun 25, 2019
@paulhauner
Copy link
Member Author

@paulhauner paulhauner commented Jul 12, 2019

I think we should push this date back. I propose the 25/07 but I'm flexible.

@AgeManning, @spble, @michaelsproul keen to hear your thoughts :)

Loading

@spble
Copy link
Contributor

@spble spble commented Jul 12, 2019

Agreed, 25th July sounds good!

Loading

@paulhauner paulhauner removed this from the v0.0.1 milestone Oct 25, 2019
@paulhauner paulhauner closed this Nov 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants