Add network topology / software subcomponent diagram #124
Labels
content improvement
A content improvement less substantial than a design suggestion
diagram
Diagram content
Suggested Improvement
Prerequisite
Note: Before we introduce this diagram, we need a bit more confidence in the network topology and software subcomponent architecture.
Context / Assumption
The assumption behind this diagram is that a full node could be implemented with two distinct software modules roughly corresponding to "NU5-like validating full node" and a "TFL validating node" (within the same host), and then each of those subcomponents speaks a distinct network protocol to the analogous components on other nodes (and maybe not necessarily even the same hosts).
Diagram Description
Add graphic showing nodes connected to each other in the p2p protocol. Each node has two parts: PoW and TFL. Each part has a distinct connection to the neighbors of the same part, so node A's "PoW" connects to node B's "PoW", node A's "TFL" connects to node B's "TFL". Finally, we want some way to visualize that all of the PoW nodes and connections were "pre-existing" and that the TFL pieces are a "new layer".
Example
The introductory blog post already has a pretty image for this:
The text was updated successfully, but these errors were encountered: