Use decentralised naming service for getting shielded address for ARRR

[satindergrewal]

The idea of using naming service for getting ARRR address for a user is to just use the decentralised name to send/receive ARRR in wallet. The naming services support we can aim to add in Phase X can be:

• [ ] ENS Name Service
• [ ] VerusID - Example - mike@
• [ ] Handshake

[satindergrewal]

I'll try to get the APIs examples and things required to set these up, and document here for future reference, which we can follow and build the feature in our wallets.

[satindergrewal]

For ENS:

• https://docs.ens.domains/dapp-developer-guide/resolving-names
• https://github.com/argentlabs/web3.swift
• Setting up own ETH node:
  • https://ethereum.org/en/developers/docs/nodes-and-clients/#advantages-of-different-implementations
  • https://ethereum.org/en/developers/docs/nodes-and-clients/run-a-node/
• https://blog.cloudflare.com/cloudflare-distributed-web-resolver/

EDIT 1: The target with ENS service would be to:

• Setup own ETH node server and use that as RPC server for to query ETH blockchain.
  • Trying not to depend on 3rd party ETH API provider service like infura.io if possible.
• Make a small code which queries this ETH node, and returns the .eth output through an API
• Make this .eth resolving code for wallets open source and document for others to setup it on their own infrastructure if they wish to.