Network Topology

Staex MCC supports several network topologies to fit different deployment requirements. Nodes connect to the network through parent nodes, and the arrangement of these parent-child relationships determines the overall topology.

In a tree topology, multiple nodes point to the same parent. This is the most common configuration and works well for centralized deployments:

# Node A
sudo mcc init --parents public.staex.io <NETWORK-CERTIFICATE-BASE64>
# Node B
sudo mcc init --parents public.staex.io <NETWORK-CERTIFICATE-BASE64>

Both nodes register with the same parent (public.staex.io), forming a tree where the public network acts as the root.

In a linear topology, nodes are chained together: each node connects to the previous one as its parent.

# First node connects to the public network
sudo mcc init --parents public.staex.io <NETWORK-CERTIFICATE-BASE64>
# Second node connects to the first node
sudo mcc init --parents <FIRST_NODE_IP>:9376 <NETWORK-CERTIFICATE-BASE64>

This configuration is useful when nodes are physically distributed and only have line-of-sight connectivity to their immediate neighbor.

Staex MCC ensures global connectivity even when a child node can only reach its immediate parent. Traffic is automatically forwarded through the chain of parent nodes until it reaches the destination. You can chain-link nodes to build multi-hop networks that span geographically dispersed locations, enabling communication between endpoints that have no direct path to each other.