vacp2p
/
rfc
mirror of https://github.com/vacp2p/rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

30: sigh, filename fmt

This commit is contained in:
Oskar Thoren 2021-09-01 19:00:02 +08:00
parent 33ca33d48b
commit 03e93b4bbc
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/docs/rfcs/30/README.md
View File

@ -53,7 +53,7 @@ Incentives to run a node is currently planned around:
Each node can choose which protocols to support, depending on its resources and goals. Each node can choose which protocols to support, depending on its resources and goals.
![Protocol selection](../../../../rfcs/30/adaptive_protocol_selection2.png) ![Protocol selection](../../../../rfcs/30/adaptive_node_protocol_selection2.png)
In the case of protocols like 11/WAKU2-RELAY etc (12, 13, 19, 21) these correspond to Libp2p protocols. In the case of protocols like 11/WAKU2-RELAY etc (12, 13, 19, 21) these correspond to Libp2p protocols.
@ -69,11 +69,11 @@ We can better visualize the network with some illustrative examples.
The first one shows an example topology with different PubSub topics for the relay protocol. The first one shows an example topology with different PubSub topics for the relay protocol.
![Waku Network visualization](../../../../rfcs/30/adaptive_network_topology_protocols2.png) ![Waku Network visualization](../../../../rfcs/30/adaptive_node_network_topology_protocols2.png)
## Legend ## Legend
![Waku Network visualization legend](../../../../rfcs/30/adaptive_network_topology_protocols_legend.png) ![Waku Network visualization legend](../../../../rfcs/30/adaptive_node_network_topology_protocols_legend.png)
The dotted box shows what content topics (application-specific) a node is interested in. The dotted box shows what content topics (application-specific) a node is interested in.