blueskyCommunity / aozora

MIT License
108 stars 24 forks source link

Thoughts on naming in the decentralized future #9

Open SpokieKid opened 3 years ago

SpokieKid commented 3 years ago

I (Paul Webb) compiled my thoughts in this file, may be a bit jumbled haha.

Imported from Gitlab. See Original.

AaronGoldman commented 2 years ago

There a three kinds of names that you need to consider Address, Fingerprints, and Tags.

An address is a combination of a consensus algorithm and a chosen name. Typically this is done with a centralised authority but could also be done with a consensus group of limited trust parties or even a public legger. example@gmail.com, twitter handel, phone number, zip code street house number, ... The DNS system is an example of address as is the ENS (Ethereum Name Service) and Handshake

The second type is the fingerprints. Typically this is as hash. It could be your public key, a hash of your public key, or the hash of a certificate. I could have a cert that provides my keys:

{
  "Public key":"{key}",
  "Revocation key":"{key}",
  "Revocation uri":"{URL}",
  "Rotation key":"{key}",
  "tags": ["my_cool_name"]
}

and my fingerprint could be the hash of that cert. examples of fingerprints are Bitcoin wallets, .onion domains, miniLock IDs

Lately we have tags they are not secured by ether a consensus algorithm or large random numbers. Anyone can add a tag to any address or fingerprint this can be very useful for ID as search. Say I go searching for XKCD and I get a few hits for Id that have this tag. I look at the IDs and decide the one linked to xkcd.com, https://twitter.com/xkcd, and tagged as "Randall Munroe" is the one I want so I add it's fingerprint to my address book. The tag did not give me a single ID but did narrow it down to a point I could audit the other assertion and find the ID I wanted.

address yourname.eth
fingerprint 234567abcdefghij
tag Paul_Webb
AaronGoldman commented 2 years ago

There a three kinds of names that you need to consider Address, Fingerprints, and Tags.

An address is a combination of a consensus algorithm and a chosen name. Typically this is done with a centralised authority but could also be done with a consensus group of limited trust parties or even a public legger. example@gmail.com, twitter handel, phone number, zip code street house number, ... The DNS system is an example of address as is the ENS (Ethereum Name Service) and Handshake

The second type is the fingerprints. Typically this is as hash. It could be your public key, a hash of your public key, or the hash of a certificate. I could have a cert that provides my keys:

{
  "Public key":"{key}",
  "Revocation key":"{key}",
  "Revocation uri":"{URL}",
  "Rotation key":"{key}",
  "tags": ["my_cool_name"]
}

and my fingerprint could be the hash of that cert. examples of fingerprints are Bitcoin wallets, .onion domains, miniLock IDs

Lately we have tags they are not secured by ether a consensus algorithm or large random numbers. Anyone can add a tag to any address or fingerprint this can be very useful for ID as search. Say I go searching for XKCD and I get a few hits for Id that have this tag. I look at the IDs and decide the one linked to xkcd.com, https://twitter.com/xkcd, and tagged as "Randall Munroe" is the one I want so I add it's fingerprint to my address book. The tag did not give me a single ID but did narrow it down to a point I could audit the other assertion and find the ID I wanted.

address yourname.eth
fingerprint 234567abcdefghij
tag Paul_Webb
NetOpWibby commented 1 year ago

Should I open a new issue? This was my issue in Gitlab but I didn't know it was moved until just now.

AaronGoldman commented 1 year ago

up to you