Noosphere component which is a transport layer for Link Records. It’s not inherent to the noosphere protocol because Link Records can be resolved through other means (which we refer to as syndication layers). Maybe, one day we use a different resolution mechanism (it’s important enough that maybe subconscious shouldn’t own this given our size).
It is a mapping of sphere DID to the Link Record called an Noosphere Identity.
Need to re-publish orb-ns records every ~2 days (soft and unspecified at the protocol level) because we eventually want to drop records no one cares about.
Because of propagation and they are UCANs, the resulting records are time-bounded.
Unlike IPNS, orb-ns resolves a key to a data structure, not a running IPFS node. This has positive scaling characteristics b/c you don’t need lots of nodes for multi-tenancy.