Does Storj Support ENS? (ethereum name service)

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
wallet2.air.eth
new.air.eth and so on

3 Likes

Can you elaborate whats the use of ENS in Storj ?

I would like to see this enabled so that I could have a clearer payment path and accounting. There’s also something to be said for creating a business ENS domain in order to easily show business income or loss versus personal income.

Of course, ENS is superfluous. However, the subdomain naming conventions along with a little Solidity smart contract work could make for a nice flow chart tax report.

And… then there’s the benefit of not making a copy/paste error when creating your node and accidentally sending all your STORJ to someone else.

I am lost here. How is creating node related to sending payments ?

If I understand this correctly Storj should own a domain under ENS so SNOs can better understand payments.

-e WALLET="payments.domain.ens"...

is much easier to write than:

-e WALLET="0x729b..."

Ohh so instead of sending payment to “0x729b…” it should send it to “payments.domain.ens”. This domain would be owned by SNOs to easily remember the payment address but Storj should support paying to ENS domains. Did I get that right ?

1 Like

Yes. That’s correct.

Of course, this is a “nice-to-have” feature request. I’m sure there are more pressing coding issues.

Here are the ENS github docs

EDIT:

It’s also good to have general idea of how supporting ENS may create a easily automated path for bidirectional payments…

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.

1 Like

OP or you should make a post on ideas.storj.io for the same

2 Likes

I dont think this serves any benefits to storj most of us use a wallet that we can see our transactions, and in your dashboard it links direct to your wallet on eth. If this is based on only the fact its easier to remember it kinda defeats the purpose of using a wallet where you can copy and paste the address.

Let’s say there was a family/friend network running multiple SNs in several geographical areas.

Let’s say some of those family/friends were not very tech savvy.

Let’s say the tech savvy SNO of the group sets up an ENS domain and creates a subdomain for each member of the group.

Then, instead of having the non-techies entering in 0x715ce... ---- they can simply enter alice.domain.eth or bob.domain.eth … as in some other thread, the TOS of one SNO per payment address would be adhered to, while also allowing for easy tracking of which address belongs to which node.

Again… ENS is superfluous, smart contracts will work without ENS subdomains for my above example of automated payments loop and entering in the hex ETH address works just fine.

But, that doesn’t mean ENS support wouldn’t be useful and a “nice-to-have” feature.

But you have to understand something, If it aint broke dont fix it adding a feature thats based on a DNS service isnt the way to go, call me old fashion but if your doing crypto you need to be somewhat tech savy in the first place. No one is going to be doing crypto if they dont understand how the wallets work. Sure it makes thats easier to remember but we been doing this for years. Sometimes adding something new to the table just adds point of failure. Having the exact wallet address is always #1.

1 Like

Brave Browser is an example of attempting to bring Crypto to the masses.

No one types in IPv4 addresses to get to Google… but you can. Understanding the underlying technology is a great goal, but not everyone “in Crypto” is going to understand what’s going on under the hood. The number of persons accumulating some Crypto expanded tremendously in 2019… and 2020 looks to be an explosive year. My guess is by 2025, most humans who have Internet access will have some amount of Crypto… and only a smattering of those persons will understand what’s going on under the hood.

I don’t know if would call brave browser bringing crypto to the masses though, Its more like people want to make money for doing nothing just by running a browers, what they dont understand is its just a way to lock you into there crypto and making it harder to get it out of there wallet.

But your also not dealing with money depending on a dns to make sure its up and running when the payment gets sent.

To the point just made by @deathlessdd please note that on their own website https://ens.domains/ 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 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.

6 Likes

I’ve been running Brave Browser since before BAT payments were active and I have had zero issues with Brave and BAT payments.

The only requirement is to pass Uphold’s KYC… Uphold charges zero fees to withdraw BAT from their custodial wallet to a personal wallet. The KYC requirement is a regulatory requirement which has nothing whatsoever to do with Brave or BAT. KYC is the law in many countries and that requirement is expanding rapidly.

In the USA, reporting of any and all Crypto is now required by the IRS. So, for any USA SNOs if you received 0.0000001 STORJ in 2019, you are required to answer the crypto-currency question in the affirmative.

The days of anonymous payments are ending rapidly. It’s just the way it is… I expect Storj/Tardigrade to be leaned on by various regulatory departments soon as well.

This is a valid concern. However, support for sending payments to ENS domains shouldn’t impact those SNOs wishing to enter in a raw hex address for payments. So, a warning message regarding possible security issues should suffice for offloading lost payment responsibilities on the Storj side.

Its a minimal 600 dollars that you are required to report. If you make less then that you dont need to report anything.

I also want to point out that you have to pay for ENS services its not free so take that out of you trying to make any money ontop of your elect bill internet hardware etc.

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.

5 Likes

The payment of tax is not the same as the reporting requirement…

See this article’s advice

“Virtual currency: If, in 2019, you engaged in a transaction involving virtual currency you will need to file Schedule 1. See the instructions for Schedule 1 for more information.”

When you go to Schedule 1, the question about Virtual Currency appears right at the top.Tax form 1040
The question covers everyone who has dabbled with cryptocurrency in any fashion. Even if you just used Brave Browser and received some BAT, you are still required to answer this question as ‘Yes’.

You’ve forgotten that all traffic in and out of all SNOs goes through DNS. And all payments over the Ethereum network have security concerns unless one is running a full node locally.

It’s tempting to get into a discussion of the various merits/demerits of various networking architectures. However, at the end of the day, trust in some third party is required in order to utilize the Internet.

That statement may sound obvious or as a catch-all strawman. But it’s not.

I would still recommend making a post on ideas portal so devs can have a look at it and decide to accept/deny the feature.

1 Like