NRS Pre-Registration and Sale

According to the RFC of the NRS the names in safe will be published AppendOnlyData (versioned) so once created, as far as I understand, they can never be deleted or transferred. So I’m not sure that anyone could monetarize these names by selling them.

Another thing are the security problems or phishing that could be generated.

1 Like

To me it is to early for someone to invest $10k into nice domain, when SafeNetwork is not widely know around the world and working. The price of dot com also developed since beginning of Internet. Who would buy dot com domain for $10k 25 years ago ? Or dot tech today ?

Which is exactly the power you hope to exploit by pre registering the names yourself.

I would rather trust the maidsafe foundation to do right for the network and it’s partners, than random folk trying to make an easy buck.

1 Like

So can a name registeration be transferred?

1 Like

Transfer the account they were created in, is the easy solution.

I’ve commented on this topic at length two times prior.

The only decent SAFE solution is to publicly reserve all single words in the dictionaries of all online languages in addition to the other common domains already used like ‘org’ and ‘gov’ or country codes and publicly traded corporations. The private keys get published as the sites ‘version 0’. It becomes a public commons where groups can battle over what is published there, analogous to a wikipedia page with no censorship/lockdown. The actual version of the site that is viewed by default in the SAFE browser doesn’t necessarily need to be the most recent, but instead the version with the most ‘likes’ or ‘upvotes’. This serves as a constant stream of PUT income for the network. It would be an interesting social experiment to see what evolves. Posting the private key publicly is essentially a form of public burning that is readily proven. This is the most fair method that maintains a common de facto NRS standard.

tldr; broken record…
Because of the safe:// structure of the NRS, anyone is free to call their service as common dictionary words. Their public name would only need to be unique.

For example ‘safe://awesome.happybeing’ or ‘safe://great.traktion’ would be fine to claim, but ‘safe://being.happy’ or ‘safe://happy.being’ or ‘safe://happy’ would not because the pubIDs are single dictionary words.

Yup, this is the crux of it. The primary purpose of the NRS isn’t findability, it’s communicability.

In other words, being able to put a unique, yet human readable and orally reproducible wrapper around a XOR address.

And remember, we have other tools in the chest for findability such as linked data. No reason that can’t be deployed alongside NRS to solve the that issue, even right in the address bar.

As a wee example, think of the combination of unique Handle, plus your free choice of Name you have on twitter and how that works.

I can have primary results returned by the free name along with other profile elements if needed—and then narrowed by a socially derived priority—and finally uniquely selected/addressed with the NRS address.

I might never really need to deal with the NRS part of things often, so if all I can get is @JimCollinson38826 for my SafeID it’s not really a big deal.

This is the starting point for our way of thinking about SafeIDs BTW, and could quite rightly be extended to any site/address.


This is not suitable. The person selling the account can access the account and has the private keys to all in the account at the time of sale


I was going to answer the same thing. We must also remember that every public site, including any name, must comply with the rules of the perpetual web where history cannot be altered.

1 Like

It seems there needs to be another layer of abstraction.

If I can, then I will … and you should thank me - as if I do it, I’ll plow profits back into the network - another entity might just do it for pure profit and take the money out/away from the network.

If true that names are permanently stuck to an account, then there is another problem I’ve just thought of as well – a malicious actor (say a rival corporation) could buy up names of competitors and then make the keys to the account public - effectively neutering the use of the name forever.

Further, If you were a government and wanted to seriously hamper the network, you do the same with a dictionary and large amount of cash. Effectively trashing the defacto NRS.

Easy do not suggest people ever do it.

The other is to allow the AD to have its ownership transferred which is promised. And simply transfer ownership of the AD which holds the registration info

1 Like

It’s a difficult subject with no ideal solution I’m afraid. What I would like to see is an expiry date on the NRS name. A year, or even a month.
Then there will be an automatic auction provided by the network. The paid Safecoins return to the network.
Only the real owner is prepared to put effort in it for getting the name each time, and is prepared to pay for it. Squatting is useless now.
Maybe the current owner can have a discount of 50% on the auction price so he has an advantage for getting it back.

The reason I would prefer this, is because I really don’t like the idea that someone owns safe:\news and then he dies…
I don’t think it’s good marketing that the SAFE Network is one big graveyard of old websites.


The network isn’t aware of time as we think of it - it sees time through events. So I don’t know how that would work.


Given how attached many are to having domain names, I think the only practical solution is to have multiple NRS plugin’s and/or I2P-style lists … then we effectively have as many copies of the names as we want and the network is kinda partitioned via the plugin you use.

1 Like

One could see that as a feature. Digital archeology—a permanent record of cyber history.


Since everyone seems to agree that a well done petname system or the continuous auction system suggested by @Seneca a long time ago are not paths that look more attractive than this graveyard/squatting mess Oo

We could have a ‘sidechain’ to safe - simply not having the naming system baked into the core and the data types on safe but have the name service managed through a blockchain (==public registrar) with precisely the properties that people want the names to have (expiration/prices)


Then we use something else. Visits, votes, some other info we DO have. There must be something we can use to determine some cycle


Actually for 1 year expirstional names a blockchain would be not a bad solution at all Oo…

… You could throw away blocks that are older than 1 year and I heard that blockchains are not the worst solution if you try to utilize them as public ledger :thinking:

… Would just be nice if one could use data from safe to secure the chain instead of having to use pow…

1 Like

Jim, is NRS part of the core code or is it going to be a plugin? It seems like someone said it was ‘like’ a plugin? But don’t know what that means. I can imagine that anyone could make a browser plugin to do something akin to NRS, but if Maidsafe’s NRS is in the core, then it seems like it’s defacto nature will give it unstoppable dominance over NRS as a whole.

Perhaps a user installed NRS plugin could overthrow the in-built NRS on a site-by-site basis much like the “important” flag in CSS. Thus malicious domains captured by attackers could be neutralized through the users choice in NRS plugin … I’m rambling here, but maybe you get the idea.

1 Like

A really bad feature. We got history behind that history button, that’s ok. But the current owner should be someone alive