-
Notifications
You must be signed in to change notification settings - Fork 85
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
Staged Test Network Plan #116
Comments
Proposal for DevConnect goals:
|
Does this include 1) and 2) from Phase Two: Gossip? |
I think it can be done in whatever the fastest/quickest way that works is which doesn't diverge too far from the existing roadmap. Don't want us doing extra work that doesn't lead us towards the final product... but if we can have uTP streams by then in any capacity then huzzah! |
Have updated for Ultralight |
As have I for Fluffy |
Updated for Trin |
is 🍕 a no? partial? |
Partial in our case |
Partial/in progress for Trin. Updated POKE with ❌ as It is not yet implemented. |
POKE in trin is merged, I updated the table |
Closing as this is completed since a while for all clients mentioned in the issue tracker. |
I would like to outline some proposed structure for how we roll out our test network.
The goal of this test network is to iterate towards the full functionality necessary for the Chain History network.
Phases
Phase Zero: Overlay Only
During this phase we will simply establish our ability to establish a stable overlay network using the Portal Wire Protocol messages.
0x500B
(History Network)In this phase, each team will be responsible for deploying however many nodes they wish. Each team may supply the ENR records for any stable "bootnodes" they will be operating.
What we are testing:
Phase One: Simple Content Retrieval
During this phase we will be testing the ability to find and retrieve content stored in the network by other nodes.
content-id
content-key
format for headers referenced by their block hash.What we are testing
Phase Two: Gossip
During this phase we will build out the mechanisms needed for gossip, including use of the uTP protocol.
content-key
and validation of the block header.What we are testing
Phase Three: Head Tracking
Phase Four: Full Content Transmission
During this phase we will flesh out the remaining functionality for transmission of content, specifically, large payloads that must be sent over uTP
connection-id
, the client initiates a uTP stream and receives the content payload over the stream.What we are testing
Phase Five: The Road To Production
The text was updated successfully, but these errors were encountered: