draft for alternative namespace resolution standard proposal

[ca98am79]

No description provided.

[Falci]

Please, use the number HIP-0005

[pinheadmz]

This is probably going to change as we work on the actual implementation. Let's hold off on merging this HIP until something works ;-)

[ca98am79]

this didn't end up changing with our implementation, so I assume we can merge this now

[kibagateaux]

Is there some standard registry we can use for these network codes so they can be easily looked up / derived programmatically? I remember seeing some list from trezor or something that gets used a lot but can't find it now. E.g. someone might put _eth but they actually mean the Ethereum Classic chain (ETC) or I want my MetaMask to update a file for this hsd plugin that automatically rejects resolution to networks that I haven't configured in my wallet.

Not exactly the same but similar to this https://github.com/multiformats/multiaddr

[tynes]

Is there some standard registry we can use for these network codes so they can be easily looked up / derived programmatically?

I think keeping a list in this HIP would be appropriate. I feel like we should be sure to make this standard flexible enough to support more than just delegation to other L1 blockchains, for example being able to delegate to a nameserver that is discoverable via tor. It appears as though this should be possible with the current scheme, but I don't know all of the details in practice. Any other thoughts on what this standard could be used for?

[pinheadmz]

Any other thoughts on what this standard could be used for?

I see it being expanded to virtual off-network TLDs like ._footnote and ._ipfs