We at NetSys make an effort to finally realize (seed-labs#24).

Abstract:
Within a simulation several layers of overlay networks ( i.e. DNS infrastructure, Botnet, Darknet, Blockchain, IPFS etc.) can be established on the same physical network topology (which is the only thing that is currently displayed in the clients map-view). Often the overlay is what we're actually interested in and would like to examine. In such cases the physical underlay visualization is only distracting and one should be able to disable it in favor of the overlay.

Relevance:
This feature will amplify SEEDS usefulness as an educational tool i.e. for use in our Advanced Topics In Networking (ATN) lecture. Students could i.e. observe overlay DHT formation or content routing according to some algorithm (kademlia, cord etc. ). Completion of this milestone will render SEED on par with dedicated P2P simulators such as overlay weaver , facilitate engagement with the P2P / web3 topic and lower the entry hurdle.

Implementation:
To distinguish nodes and associate them to the right overlays there already exist the 'displayName' and 'Class' container meta labels (set by the docker compiler ) based on which the frontend can discern participation in layers.

The client UI has to be extended by a Quick Action API that lets the user select which layers should be visualized and which shouldnt (physical underlay, DNS, ... ).