Author Topic: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!  (Read 17173 times)

0 Members and 1 Guest are viewing this topic.

Offline fuzzy

Those of you who know me, know how passionate I am about saving the Internet.
 
Some warnings:
Wikileaks Loses DNS Service, Supporters Spread Mirrors as 'Infowar' Continues
  http://techpresident.com/blog-entry/updated-wikileaks-loses-dns-service-supporters-spread-mirrors-infowar-continues
What do UK and Iran have in common? Both want to outlaw encrypted apps
  http://www.theregister.co.uk/2015/01/12/iranuk_in_accord_as_pm_promises_to_block_encrypted_comms_after_election
David Cameron wants to ban encrypted apps like iMessage and Whatsapp
  https://nakedsecurity.sophos.com/2015/01/14/david-cameron-wants-to-ban-encrypted-apps-like-imessage-and-whatsapp
Russia (and Bangladesh, Vietnam, Iceland....) on blocking crypto-related websites:
  http://cointelegraph.com/news/113857/russias-bitcoin-ban-expected-in-august-expert-recommends-businesses-get-out
NameCoin slips further, down to #15 on CMC today:
  http://coinmarketcap.com
 
Our wallets (wallet.bitshares.org, moonstone, bitsharesblocks, metaexchange, etc) are at stake now, not just the web itself.
Let's save ourselves first, then begin work on integrations with icann/iana/ietf, etc.
 
My ideas:
1. Make a chrome browser extension (for now) that uses the proven BitShares Login (see below).
2. If the extension sees an address/url of "bts:web.kencode" it will check the routable location to that "child" (website).
2b. You could even have the website owner maintain their own json file w/routing keys/vals, ie: http://kencode.de/id/kenCode.json
3. If the extension sees "bts:kencode/approve" it will load up the local client, or the web wallet as a backup for votes.
4. If the extension sees "bts:web.kencode/approve" you could vote for a website's popularity, great for search algos.
5. If the extension sees "bts:chat.kencode" it would load up the user's chosen voip Dapp (like icq, firechat, tweets, skype).
6. If the extension sees "bts:mail.kencode/subject?'Here's my subject line'" it would load up the user's chosen email client.
 
Once the extension has these basic abilities, then we could connect it to volunteer bridging nodes to ip4/ip6 tables. I will happily host the first few myself by purchasing a dedicated ip from my isp. I'll host my kencode website on a beaglebone black, or one of my raspi's. This way, you guys can verify routing and mapping to the "web" child account as seen in #2 and #4 above.
 
Here's a list of people that I have seen in discussions regarding BitShares DNS, may be qualified:
A. @indolering
B. @toast
C. @gamey (https://bitsharestalk.org/index.php?topic=12119.0;all)
D. @testz (https://bitsharestalk.org/index.php?topic=12540.0;all)
E. @bytemaster (http://bytemaster.bitshares.org/article/2014/12/22/BitShares-Login/)
F. Am I missing anyone??
 
If this Poll is successful, I see no reason why we can't get the first extension up and running ASAP. The technology already exists.
 
Think of how newsworthy this will be when released with 1.0.
First Moonstone, then BitShares DNS!
(the Darknet subreddit has become VERY active the last 6 months, and for good reason!)


The Browser is the best idea ever.  I have been telling everyone this is what we need more than anything else...but I have absolutely no clue where to start. 

I personally think Toast should be working on a separate DNS chain, and then working with BitShares on the side to add the same capability to BitShares.  There would be no incentive for him not to and every incentive for him to do it. 

Of course, then again I think the 1.0 client should probably be released first and foremost.

As for Moonstone.  I'm pretty certain it is a winner out of the box.  Everything they do is so professionally done that it is really hard to believe their product won't be similarly fabulous.
« Last Edit: April 04, 2015, 06:47:17 pm by fuzzy »
WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline Thom

Thanks so much for for your (relative) newbie perspective of just how important DNS is.

When I think back on how many resources in the past year have been considered more important than DNS I get a very bad feeling in my stomach. DNS is one of the foundational elements that brought me into this community, and like you kenCode I feel very passionate about it.

I don't think the primary obstacle to rolling out a solution is technological, but is rather methodological. The heart of the problem is how to provide open access the the namespace in a manor that best serves all parties. Since some of these parties have conflicting interests the solution is a mater of vetting proposals and building consensus to implement the one chosen. It is largely an issue of what does consensus look like and how is it measured.

In the early days before DNS disappeared from focus there were a few proposals made, but none that seemed overwhelmingly satisfying to me personally. If I recall correctly the auction proposal was the predominate front runner. It is probably the best choice, but my fear is getting a simple name (without conflict with other) could take time to go thru a bidding process and I would need to expose my choice to others potentially taking it away from me to use. If I came up with a catchy, clever name that others find appealing and someone else who had no direct interest in it (other than to resell it), someone could come along and take that away from me.

Some say, well, that's the free market. Others might say, "but I invented that name" and feel it thus belongs to them. The former might say those with the most money will always win, and poor clever wordsmiths never do, is a potential outcome. And then there is the issue of migration & name ownership. Should somebody be able to squat on names like IBM, Microsoft, TrumpEnterprises etc. in the new DNS namespace and devise schemes to hold on to such names (in an auction system) long enough to sell them at huge profits to those who own those names in the existing DNS?

I believe it would be trivial to implement DNS on the blockchain compared to many of the features BitShares has already implemented. I see these issues as the reason DNS lost steam, the community (including the dev team) just couldn't come to a consensus. Where is Brent Allsop (canonizer.com) to help with this specific issue when you need him?
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
I have tried to contact him directly thru his indolering.com website, as well as here on the forum.
No luck.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
IMO the DNS stuff should be done properly, and that takes time. If we rush out a half-baked solution we'll regret it later.

But you are right insofar as there doesn't seem to be any development on that front, and we should get this moving. What has become of Indolering's excellent proposal?
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Those of you who know me (ken@bitshares-munich.de), know how passionate I am about saving the Internet.
 
Some related reasonings:
Wikileaks Loses DNS Service, Supporters Spread Mirrors as 'Infowar' Continues
  http://techpresident.com/blog-entry/updated-wikileaks-loses-dns-service-supporters-spread-mirrors-infowar-continues
What do UK and Iran have in common? Both want to outlaw encrypted apps
  http://www.theregister.co.uk/2015/01/12/iranuk_in_accord_as_pm_promises_to_block_encrypted_comms_after_election
David Cameron wants to ban encrypted apps like iMessage and Whatsapp
  https://nakedsecurity.sophos.com/2015/01/14/david-cameron-wants-to-ban-encrypted-apps-like-imessage-and-whatsapp
Russia (and Bangladesh, Vietnam, Iceland....) on blocking crypto-related websites:
  http://cointelegraph.com/news/113857/russias-bitcoin-ban-expected-in-august-expert-recommends-businesses-get-out
Why Namecoin Didn't Take Off: A Cautionary Tale
  http://cointelegraph.com/news/114129/why-namecoin-didnt-take-off-a-cautionary-tale
Tesla wants DNS Decentralized
  http://cointelegraph.com/news/114149/adopting-the-chain-how-tesla-could-protect-its-website-and-its-cars
 
Our wallets (wallet.bitshares.org, moonstone, bitsharesblocks, metaexchange, etc) are at stake now, not just the web itself.
Let's save ourselves first, then begin work on integrations with icann/iana/ietf, etc.
 
More ideas:
1. Make a new chrome browser extension that uses the proven BitShares Login (see below).
2. If the extension sees an address/url of "btsd:web.kencode" it will check the routable location to that "child" (website).
2b. You could even have the website owner maintain their own json file w/routing keys/vals, ie: http://kencode.de/id/kenCode.json
3. If the extension sees "btsd:kencode/approve" it will load up the local client, or the web wallet as a backup for votes.
4. If the extension sees "btsd:web.kencode/approve" you could vote for a website's popularity, great for search algos.
5. If the extension sees "btsd:chat.kencode" it would load up the user's chosen voip Dapp (like jitsi, firechat, icq, tweets, skype).
6. If the extension sees "btsd:mail.kencode/subject?'Here's my subject line'" it would load up the user's chosen email client.
 
Once the extension has these new abilities, then we could connect it to volunteer bridging nodes to ip4/ip6 tables. I will happily host the first few myself by purchasing a dedicated ip from my isp. I'll host my kencode website on a beaglebone black, or one of my raspi's. This way, you guys can verify routing and mapping to the "web" child account as seen in #2 and #4 above.
 
Here's a list of people that can assist with our Decentralized DNS Working Group (DDNSWG):
A. @toast at NOTE
B. Vitalik at ETH
C. Bas at NXT
D. Oleg at EMC
E. Elon Musk (we love Tesla)
F. @indolering at NMC
G. @gamey (https://bitsharestalk.org/index.php?topic=12119.0;all)
H. @testz (https://bitsharestalk.org/index.php?topic=12540.0;all)
I. Am I missing anyone??
 
The technology is already here, we just need to work together to finish it up. Please vote in the Poll above! :)
 
Think of how newsworthy this will be when released with 1.0.
First Moonstone, then decentralized BitShares DNS! (DDNS)
(the Darknet subreddit has become VERY active the last 6 months, and for good reason!)
« Last Edit: May 06, 2015, 01:35:28 pm by kenCode »
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat