elective-stereophonic
elective-stereophonic
New alias type for serialized data  
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Author Topic: New alias type for serialized data  (Read 681 times)

toenu

  • Full Member
  • ***
  • Karma: +52/-1
  • Offline Offline
  • Posts: 231
    • View Profile
New alias type for serialized data
« on: August 07, 2014, 11:14:26 am »

After getting DNS with alias system to work, something to me has become obvious:

The client needs functionality to store arbitrary serialized data in an alias. (A JSON object being the natural choice)

This should just be another alias type, in addition to URI, Account and Other.

The JSON data can be gathered from a simple form like this: (a form like this should be part of the client)
http://www.nxtresource.com/aliasform/

I suggest the new alias type to be called "Identity". Which fields this should include by default should be subject to discussion. I pretty much just copied the namecoin specifications. If you have suggestions, let's hear them.
In the client the user should be able to create any new fields, which my example form can not do.

The client does not need to change the way it is displaying alias data. This is simply to store data in a structured way on the blockchain for other applications to use.

For DNS specific fields we should stick with namecoin spec. They have already done pretty much all of the work and it's good to have a common standard with other blockchain based namespaces.

A nice additional feature to have would be to optionally save an identity only locally and sending out as an encrypted message, kind of like a business card.

Pros:
- The alias system becomes much more useful (Today it is barely used at all)
- Completely client side, no change in architecture needed - can be done today
- Implementation should be quite easy
- Enables use of aliases for DNS
- If people start storing information about themselves on the blockchain like this, Nxt basically has the groundwork for a decentralized social network
- The same can eventually be done with other transaction types - like perhaps an order form where you put your contact info for marketplace purchases.

Cons:
- Can't think of any


I hope it is very clear what I mean. Please discuss.
Logged

websioux

  • Sr. Member
  • ****
  • Karma: +69/-1
  • Offline Offline
  • Posts: 343
  • Great changes grow bottom up
    • View Profile
    • Scriba.io the Blockchain Scribe
Re: New alias type for serialized data
« Reply #1 on: August 29, 2014, 05:16:10 pm »

Is a new field (dns or identity) really necessary ?
Why not use the other field ?
if you find a json there that corresponds to a nxt dns spec like the one you are building then it is one otherwise not.
Logged
Secret Miner <= communicate with style | NotBot <= timestamp digital docs
 

elective-stereophonic
elective-stereophonic
assembly
assembly