The IPFS routing system utilizes "content provider records" hosted on a distributed key-value store to resolve content providers. These records can include cryptographic proofs, ordering information, record freshness-guarantees; and allows nodes storing records to discard invalid, old, or "less good" records.
Use whatever resources available to you, in order to come up with a visual representation of the topic that can be projected on to a poster (similar in spirit to the poster description but with whatever creative freedom your group prefers :^)
- How do nodes signal that they're providing content?
- What options and formats exist around this?
- What other routing methods are there?
ipfs-inactive/faq#48 (comment)
https://github.com/libp2p/go-libp2p-kad-dht/blob/master/routing.go#L391
https://github.com/libp2p/js-libp2p-kad-dht/blob/master/src/providers.js
https://github.com/libp2p/js-libp2p/tree/master/examples/peer-and-content-routing
https://github.com/libp2p/specs/blob/master/IPRS.md