Core Address Resolver

[szkl]

A core can have a designated custom name, domain name, or an alias. The address resolver core is responsible for translating the name to the address in its context. The context could be global, an organization, or an application.

[Cosmin-Parvulescu]

Could cores be part of a p2p network, touched upon by @alfl in #257? If they had an append-only log, shared between themselves, perhaps persisted from time to time to the IPFS network, the cores could be part of a 'permission' and 'naming' mesh.

You could have the naming core write to this ledger, the permission core updating it. The same crypto rules would apply in the sense that appending and extracting data from this mesh would involve cryptographic identities and signing functions so we could theoretically also have a 'listing' core that perhaps ties into @billkube 's vision (You can make your own ideas and search for new ones by using the idea browser at idea.kubelt.com.) i.e. you can have a core that knows how to read the public p2p naming ledger and thus can give you a view of the entire public core mesh.

[maurerbot]

Yeah, this resolver would need to happen via our gateway. Theoretically we can use DNS records, ENS records, etc in the future and query them client side similar to dns linking in IPNS.

[billkube]

would it need to happen via the gateway for business reasons?

I think it's very useful to have some kind of naming at every level of the architecture. As @szkl says, could be used internally in an application, across a LAN or globally. kubelt could offer a global service, and maybe there are other naming services or p2p/mesh style naming that resolves core addresses as well.

[maurerbot]

Looking at the quicknode URLs I think we can provide something similar.