I’m not 100% sure what you mean, but hopefully my answer is still helpful. Content routing is performed by a DHT, so nodes do indeed maintain a lookup table [0

I’m not 100% sure what you mean, but hopefully my answer is still helpful. Content routing is performed by a DHT, so nodes do indeed maintain a lookup table [0] from hash to “provider” (i.e. an address) but a given node does not store all such mappings, only a subset. [0] It is possible to run a node in DHT “client mode”, in which case it stores no mappings and relies on peers to resolve content ids. Does this answer the question at the level you were hoping for?