How IPFS peer nodes identify each other on the distributed web

One of the key features of the distributed web is being able to access data by its content, rather than its location — the idea of content vs location addressing. This allows users to access data efficiently from any peer that has the data they want. But this idea doesn’t stop with content. A peer’s location can also change over time (native roaming) and even hop between multiple devices (runtime freedom). This would be impossible with traditional location-based addresses (like IP addresses), where you would reference peers by their network location.


This is a companion discussion topic for the original entry at https://blog.textile.io/how-ipfs-peer-nodes-identify-each-other-on-the-distributed-web/