I've modified the NIP-ND, specifically kind:61600 and kind:62600, where it now does what I mentioned previously. This means that after one acquires an ID, they can have multiple names under it that lead to different servers/sites, without needing to register a new ID. Example: - You've managed to acquire the ID nABCPoolDog. - By default, it goes to the first IP, and the first/primary name (found in kind:61600). So "desiredName.nABCPoolDog" leads to the same server as "nABCPoolDog" (note: nothing is case-sensitive). - However, after setup, otherName1.nABCPoolDog leads to a different server/website, otherName2.nABCPoolDog leads to a third different server/website, and so on. It's like you bought a ".com" and you can have whatever domain you want under it. "name1.com", "name2.com", and so on, without requiring an additional Bitcoin transaction. With that change, the protocol is now much more scalable and cheaper than before, without breaking multiple parts of it or changing its core registration/acquisition process. With a single registration/acquisition, you can have however many domains you desire, only restricted by the file size that the DNN node operators allow in their policy. Note: nABCPoolDog as a social identity, like here on nostr, will resolve to itself and/or to the first/primary name only, which is equal to the npub that owns that 'nABCPoolDog'.