I’m loving NRS - it makes DNS feel truly antiquated!
Being able to link any XOR URL to a NRS URL is intuitive and fast. As discussed long ago on this forum, the XOR URLs now feel a bit like IP addresses and NRS feel like DNS names over the top of them.
It’s so intuitive to use and easy to add and update names, e.g.
safe nrs add traktion.wallet -l safe://hnyybyqywot7fkz6beg659ugqnj5d8mpmwtbokbet5em7kknju1cfjnt3ky9e
NRS Map updated (version 1): "safe://traktion.hnyydyznicachwijpc5xtjn6ghrhbgmue3jda6i8oh6mmdswxiy5nrq9thbqh"
+ traktion.wallet safe://hnyybyqywot7fkz6beg659ugqnj5d8mpmwtbokbet5em7kknju1cfjnt3ky9e
safe wallet balance safe://traktion.wallet
Wallet at "safe://traktion.wallet" has a total balance of 6.100000000 safecoins
safe nrs add traktion.wallet -l safe://hnyybyqywot7fkz6beg659ugqnj5d8mpmwtbokbet5em7kknju1cfjnt3ky9e
NRS Map updated (version 1): "safe://traktion.hnyydyznicachwijpc5xtjn6ghrhbgmue3jda6i8oh6mmdswxiy5nrq9thbqh"
+ traktion.wallet safe://hnyybyqywot7fkz6beg659ugqnj5d8mpmwtbokbet5em7kknju1cfjnt3ky9e
safe wallet balance safe://traktion.wallet
Wallet at "safe://traktion.wallet" has a total balance of 0.500000000 safecoins
safe nrs add traktion.wallet -l safe://hnyybyc1yk541etxw5f5r4dafxp18qigy4enjsneeksy1w45a7of7cefhny9e
NRS Map updated (version 2): "safe://traktion.hnyydyznicachwijpc5xtjn6ghrhbgmue3jda6i8oh6mmdswxiy5nrq9thbqh"
+ traktion.wallet safe://hnyybyc1yk541etxw5f5r4dafxp18qigy4enjsneeksy1w45a7of7cefhny9e
safe wallet balance safe://traktion.wallet
Wallet at "safe://traktion.wallet" has a total balance of 6.100000000 safecoins
Is it possible to transfer an NRS map to another account or will this be possible in the future? I’m thinking there will be a secondary market for NRS names and it would be good to facilitate this.
As long as we can tackle the initial surge of cyber squatting attempts (such as maidsafe foundation registering the top few 100k traditional DNS names), this will be a really lovely system to live with. Anything unique will be near free and there will be a market for names which already have presence/value.
An NRS map is just another data struct (of a specific type), so in general, so long as we have the ability to modify ownership /multisig, this should be possible.
Inspect a TX status yes, definitely. For tx history we’ll need to design some optional private container that could be linked to/from a Wallet, so I’d say there could be, we’d need to work on RDF for it too so any wallet app can read/write to it, just like for the Wallet data itself.
Make it optional. One of the actual features of safecoin was NO transaction history. So any transaction history has to be optional and done by the wallet app, not by the core code.
That’s great to hear and multisig opens up some other interesting shared ownership features.
I can imagine multisig being able to delegate changes to other people, which could be actioned with the agreement of the other owner(s).
This could also open up the potential of an external market for renting a name, if you don’t want to buy it (or use it, as the owner). That is, other sig holders could allow up but transfer operations and they could have a majority to vote on transfers when required. This could be handy for a sort of ‘event’ name, that can switch to different administrators at different times (e.g. safe://football-tournament could be rented by a team/event organiser). It could also be a cheap way to have access to a popular name for a while (e.g. safe://search or some such).
Interesting possibilities, well beyond what the clunky DNS can easily facilitate.
True, but the sender with have the TX_ID still. I suppose you could still prove that you did not have any knowledge of the transaction as the receiver though, other than seeing the balance increase.
The issue is that with coins as data objects there was no Tx history and that was a strong selling point.
Now there is to be kept a Tx History. Bad selling point unless its a opt-in optional feature. And the issue i talk of is for the sender, the receiver can always without your knowledge/consent keep their own record and i am not talking of that. In that case using an anon ID provides that anonymity as far as the actual transaction is concerned. But to keep Txes then even anon IDs don’t work because there is a trail in your account showing that movement.
People were wanting the anonymity of sending coins, both for anon ID, but also no history for the time that they have to open their account for government inspection.
The transferability of domain names is a weakness of the DNS, but much less so if at all for public names in the SAFE NRS.
For example, you can take down a website just by controlling the DNS or a domain, but not with a public name because: 1) NRS is not feasible to take over, and 2) anyone can create a new name to point at a website whose name has been ‘taken down’.
We just need to know the XOR address to point the new name at, and any bookmarking system can track both, so that should never be a real problem.
Lots of things to think about in this area, and lots to like.
EDIT: it is also feasible to create your own public name for websites you visit to make your own personal, rock solid, available everywhere bookmarking system! I think there’s an app in that
Since the NRS Map is a Published AppendOnlyData, having such a private NRS system is a matter of simply creating it on a Unpublished AppendOnlyData, the resolver then works just the same
