mirror of
https://github.com/vacp2p/rfc-index.git
synced 2026-01-08 21:37:59 -05:00
update waku/informational/30/adaptive-nodes.md (#147)
Improved adaptive-nodes.md file in waku/informational/30 folder --------- Co-authored-by: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
This commit is contained in:
@@ -5,6 +5,7 @@ name: Adaptive nodes
|
|||||||
status: draft
|
status: draft
|
||||||
editor: Oskar Thorén <oskarth@titanproxy.com>
|
editor: Oskar Thorén <oskarth@titanproxy.com>
|
||||||
contributors:
|
contributors:
|
||||||
|
- Filip Dimitrijevic <filip@status.im>
|
||||||
---
|
---
|
||||||
|
|
||||||
This is an informational spec that show cases the concept of adaptive nodes.
|
This is an informational spec that show cases the concept of adaptive nodes.
|
||||||
@@ -12,7 +13,8 @@ This is an informational spec that show cases the concept of adaptive nodes.
|
|||||||
## Node types - a continuum
|
## Node types - a continuum
|
||||||
|
|
||||||
We can look at node types as a continuum,
|
We can look at node types as a continuum,
|
||||||
from more restricted to less restricted, fewer resources to more resources.
|
from more restricted to less restricted,
|
||||||
|
fewer resources to more resources.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
@@ -58,8 +60,8 @@ Each node can choose which protocols to support, depending on its resources and
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
In the case of protocols like [11/WAKU2-RELAY](../../standards/core/11/relay.md)
|
Protocols like [11/WAKU2-RELAY](/waku/standards/core/11/relay.md),
|
||||||
etc (12, 13, 19, 21) these correspond to Libp2p protocols.
|
as well as [12], [13], [19], and [21], correspond to libp2p protocols.
|
||||||
|
|
||||||
However, other protocols like 16/WAKU2-RPC
|
However, other protocols like 16/WAKU2-RPC
|
||||||
(local HTTP JSON-RPC), 25/LIBP2P-DNS-DISCOVERY,
|
(local HTTP JSON-RPC), 25/LIBP2P-DNS-DISCOVERY,
|
||||||
@@ -77,13 +79,15 @@ We can better visualize the network with some illustrative examples.
|
|||||||
|
|
||||||
### Topology and topics
|
### Topology and topics
|
||||||
|
|
||||||
The first one shows an example topology with different PubSub topics
|
This illustration shows an example topology with different PubSub topics
|
||||||
for the relay protocol.
|
for the relay protocol.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
### Legend
|
### Legend
|
||||||
|
|
||||||
|
This illustration shows an example of content topics a node is interested in.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
The dotted box shows what content topics (application-specific)
|
The dotted box shows what content topics (application-specific)
|
||||||
@@ -99,7 +103,8 @@ a topic in Waku v1 (Status chat), WalletConnect, and SuperRare community.
|
|||||||
This is a separate component with its own topology.
|
This is a separate component with its own topology.
|
||||||
|
|
||||||
Behavior and interaction with other protocols specified in Vac RFCs,
|
Behavior and interaction with other protocols specified in Vac RFCs,
|
||||||
e.g. 25/LIBP2P-DNS-DISCOVERY, 15/WAKU-BRIDGE, etc.
|
e.g. [25/LIBP2P-DNS-DISCOVERY](/vac/25/libp2p-dns-discovery.md)
|
||||||
|
and [15/WAKU-BRIDGE](/waku/standards/core/15/bridge.md).
|
||||||
|
|
||||||
### Node Cross Section
|
### Node Cross Section
|
||||||
|
|
||||||
@@ -110,8 +115,11 @@ shows how the connections look different for different protocols.
|
|||||||
|
|
||||||
## Copyright
|
## Copyright
|
||||||
|
|
||||||
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
|
Copyright and related rights waived via
|
||||||
|
[CC0](https://creativecommons.org/publicdomain/zero/1.0/).
|
||||||
|
|
||||||
## References
|
## References
|
||||||
|
|
||||||
- [11/WAKU2-RELAY](../../standards/core/11/relay.md)
|
- [11/WAKU2-RELAY](/waku/standards/core/11/relay.md)
|
||||||
|
- [25/LIBP2P-DNS-DISCOVERY](/vac/25/libp2p-dns-discovery.md)
|
||||||
|
- [15/WAKU-BRIDGE](/waku/standards/core/15/bridge.md)
|
||||||
|
|||||||
Reference in New Issue
Block a user