ENS Support

Wondering if Storj current supports or has plans to use ENS

For those that don’t know what this is. Think of DNS for IP addresses, but for wallet addresses.

www.google.com -> DNS Lookup -> 172.217.14.100
etherwallets7.eth -> ENS Lookup -> 0xF64123556abc6854f715E3cBC02Adf4434714Fc

Much easier to remember

Cost for a domain
3 letter domains = 2.412 ETH - $637.06 USD 1year
4 letter domains = 0.603 ETH - $158.96 USD 1year
5+ letter domains = 0.019 ETH - $4.97 USD 1year

Like DNS, ENS operates on a system of dot-separated hierarchial names called domains, with the owner of a domain having full control over the allocation of subdomains. -ENS

Example if you owned: air.eth

You can use as sub-domains
wallet1.air.eth = wallet1 address
wallet2.air.eth = wallet2 address
new.air.eth = wallet3 address

 

https://github.com/ensdomains/docs

 

--From Beast--

ENS domains and subdomains can also be contract addresses… so it’s possible to create the following loop:

  1. Running SNO
  2. Payment comes in
  3. Smart contract divides incoming payment and sends partial funds to outgoing_storj_subdomain
  4. Second smart contract sends STORJ tokens out Tardigrade

Two simple smart contracts and a few ENS subdomains and running an SNO becomes an automated payment loop for an SNO’s own use of the Tardigrade network.

--End Quote--

  • Aeonaura
  • Feb 14 2020
  • Attach files
  • Helene Unland commented
    14 Feb 15:47

    Please note that on their own website https://ens.domains/ 1 they state the following: Human readable names for the Ethereum network. Managing the **ENS** Root. To facilitate the possibility of upgrades and maintenance, and in exceptional circumstances to handle problems with **ENS** , the **ENS** root will initially be owned by a multisig, with members of the Ethereum dev community as keyholders. - this means that you are not exclusively in control of your ENS, but some unnamed members of the “Ethereum dev comunity” are in control. So essentially, you are putting full trust into these particular devs. Do we really want to introduce trust issues into the Storj network? They already had to exercise the ENS Root keyholders’ powers once to completely replace the ENS registry contract because of this recent bug 1 which would have allowed name transfers to be reversed by nefarious actors. In short, I don’t believe that Storj should facilitate naming conventions that may introduce these types of problems.

    Furthermore, adding this feature would result in excessive work load on support having to track down ENS related security issues, as users would invariably first blame Storj for any related issues and lost payments regardless of any warning messages we implement. I will advocate against implementing any feature that requires warning our SNOs about potential security issues with a third party.

    See full discussion of this idea in https://forum.storj.io/t/does-storj-support-ens-ethereum-name-service/4634

  • Aeonaura commented
    14 Feb 16:34

    I'm merely saying this is will most likely become common place, assuming the adoption for the protocol hits critical mass. Not to support it right away, more food for thought and to keep an eye out.

    Tons have registered domains already. All-in-all the DNS works fine for the internet, which is mostly decentralized. No reason a smart contracts can't handle ENS. Since the payment system has already been worked on.

     

    No reason to change to this right now. They, ENS, do need to work more bugs out before high adoption will take place as you said.

  • Helene Unland commented
    14 Feb 16:55

    the quote from https://ens.domains/ was incomplete in my previous comment. Here is the full quote
    ```Human readable names for the Ethereum network. Managing the **ENS** Root. To facilitate the possibility of upgrades and maintenance, and in exceptional circumstances to handle problems with **ENS** , the **ENS** root will initially be owned by a multisig, with members of the Ethereum dev community as keyholders.```