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.

Sign up for GitHub

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

Jump to bottom

Tracking issue for [Parallell IBD] #3289

Open
lehnberg opened this issue Apr 2, 2020 · 0 comments
Open

Tracking issue for [Parallell IBD] #3289

lehnberg opened this issue Apr 2, 2020 · 0 comments
Assignees
@jaspervdm
Labels
consensus breaking Use for issues or PRs that will break consensus and force a hard fork P1: Critical Top priority for a release tracking-issue RFC tracking issue
Milestone
4.0.0

Comments

@lehnberg
Copy link
Collaborator

lehnberg commented Apr 2, 2020

This is a tracking issue for RFC000X [name tbd: Parallel IBD], RFC to be submitted

This is a placeholder issue for an RFC that has yet to be submitted.
This issue will be updated once the RFC has been proposed, and
if it becomes accepted.

Once all the above have been implemented and deployed we can close this tracking issue.
@lehnberg lehnberg added consensus breaking Use for issues or PRs that will break consensus and force a hard fork P1: Critical Top priority for a release labels Apr 2, 2020
@lehnberg lehnberg added this to the 4.0.0 milestone Apr 2, 2020
@lehnberg lehnberg mentioned this issue Apr 2, 2020
Closed
@lehnberg lehnberg added the tracking-issue RFC tracking issue label Apr 2, 2020
@ghost ghost mentioned this issue Apr 15, 2020
Open
@quentinlesceller quentinlesceller mentioned this issue May 11, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaspervdm jaspervdm

Labels
consensus breaking Use for issues or PRs that will break consensus and force a hard fork P1: Critical Top priority for a release tracking-issue RFC tracking issue
Projects
None yet
Milestone
4.0.0
Development

No branches or pull requests
2 participants
@jaspervdm @lehnberg