BitShares Forum

Main => General Discussion => Topic started by: kenCode on April 03, 2015, 04:17:25 pm

Title: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 03, 2015, 04:17:25 pm
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!)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: pc on April 04, 2015, 08:45:00 am
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?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 04, 2015, 09:03:31 am
I have tried to contact him directly thru his indolering.com website, as well as here on the forum.
No luck.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: Thom on April 04, 2015, 05:35:46 pm
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?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: fuzzy on April 04, 2015, 06:43:45 pm
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.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 04, 2015, 07:04:11 pm
... the solution is a mater of vetting proposals and building consensus to implement the one chosen...

Right, so let's keep this thread laser-focused.
List your Top 5 (highly detailed) idea(s) for how decentralized DNS should work.
1. ken Code's idea
2.
3.
4.
5.
If everybody lists their (highly detailed) idea(s) here, then I will setup an additional Poll with the Top 5 ideas from the results in this thread.
Then, the winning choice from the additional Poll will determine WHICH route we should go with DNS, and this Poll (above) determines WHEN.
 
So, EVERYONE, please name up to 5 highly detailed ideas on how you would like to see decentralized DNS work...
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: robrigo on April 06, 2015, 02:48:27 pm
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?

Talked to devs about this, and you are pretty much spot on. I think the intent is lay down some foundational work to leverage such as turing complete scripting to build DNS functionality correctly. Thom's point is also correct; figuring out a methodology that will be attractive- i.e. predictable, is the key to DNS. The auction system doesn't fulfill this as he pointed out.

At any rate I asked @indolering to comment on this thread to give us an update about launching his delegates.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 06, 2015, 03:02:01 pm
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?
Talked to devs about this, and you are pretty much spot on. I think the intent is lay down some foundational work to leverage such as turing complete scripting to build DNS functionality correctly. Thom's point is also correct; figuring out a methodology that will be attractive- i.e. predictable, is the key to DNS. The auction system doesn't fulfill this as he pointed out.
At any rate I asked @indolering to comment on this thread to give us an update about launching his delegates.

Thank you guys, MUCH appreciated for your attention to this. Please keep this thread updated, thank you :)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: crypto4ever on April 07, 2015, 06:31:30 am
v0.1 beta of the DNS can be something as simple as a taskbar widget that someone clicks, enters in a URL, it does a p2p query for the latest IP address for that site, and then displays an HTML link that the user clicks.

This way, you don't have to have any browser extensions.

You don't have to bind yourself to the dns resolver or network interface

This allows site names to map to ever changing IP addresses, from a p2p database.  It's a very "lite" client, that doesn't need a huge download.

Microsoft never shipped with utorrent or ICQ, but look how popular those were.  A little taskbar widget for Windows could really work.

v1 could be a browser plugin

v2 could be something that binds to the network interface almost like hotspot shield does..

By the way, if you expect the client to have to process regular BTS blocks, with all the other non-DNS traffic, I highly recommend against that.  You need this to be as lean and mean as possible, as a separate dedicated sidechain.

If you're worried about getting BTS to gain benefit from this, all you have to do is make registering names happen via BTS only.

But clients need to do minimal processing in order to resolve a name.  Right now, you type in a name and in milliseconds you get your answer from the root servers with only a  less than 1 kb of traffic in either direction.

That's going to be the hard part.  Designing a dedicated blockchain that hardly ever hard forks that is simple and quick, and stores very little resources on the client so it can work on phones and other small devices.


Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: fuzzy on April 07, 2015, 06:39:49 am
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?

I'm working to get him and a couple of his friends from namecoin to join us in a Mumble hangout soon.  That is going on behind the scenes.  They seemed interested, so we it is more likely than not it will happen.  :)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 07, 2015, 06:55:03 am
v0.1 beta of the DNS can be something as simple as a taskbar widget that someone clicks, enters in a URL, it does a p2p query for the latest IP address for that site, and then displays an HTML link that the user clicks.
This way, you don't have to have any browser extensions.
You don't have to bind yourself to the dns resolver or network interface
This allows site names to map to ever changing IP addresses, from a p2p database.  It's a very "lite" client, that doesn't need a huge download.
Microsoft never shipped with utorrent or ICQ, but look how popular those were.  A little taskbar widget for Windows could really work.
v1 could be a browser plugin
v2 could be something that binds to the network interface almost like hotspot shield does..
By the way, if you expect the client to have to process regular BTS blocks, with all the other non-DNS traffic, I highly recommend against that.  You need this to be as lean and mean as possible, as a separate dedicated sidechain.
If you're worried about getting BTS to gain benefit from this, all you have to do is make registering names happen via BTS only.
But clients need to do minimal processing in order to resolve a name.  Right now, you type in a name and in milliseconds you get your answer from the root servers with only a  less than 1 kb of traffic in either direction.
That's going to be the hard part.  Designing a dedicated blockchain that hardly ever hard forks that is simple and quick, and stores very little resources on the client so it can work on phones and other small devices.

I love your idea!
 
A DNS database is just that. It's a lookup service, just like utorrent as you mentioned. So, if we go with .p2p, .dac, whatever, we just need to distribute that file to nodes that would like to host it, right?
 
It's essentially becoming its own blockchain, which at a later date could be chained into the BitShares blockchain or any other dapp that wants to make use of it.
 
As you mentioned above, registration would happen the BTS way. TITAN is a great example of this, only one person can have a specific user/account name.
Since I have already registered username kencode then I guess this means that kencode.p2p is mine already. I had to pay some BTS to get it, not much, but it was something.
 
Squatting: This is the tough one. Make the domain more expensive? Require votes from the community via your "delegate business plan" for use of that domain? This leads back to my idea at the top for this. The delegate name is the "web" hostname in a sense. A 0% payrate, but must be voted on nonetheless. Keybase.io has an interesting "proof of use" model for this too. The more links to other social/web accounts you own, the better.
 
The lite client you mention is awesome, we could start out with that, no gui really, just a tiny popup, like icq.
I'd be willing to run a full node of course to assist resolutions.
 
So, now we just need a coder to make the little icq-style popup app, and we need to clarify the squatter issue..............
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 07, 2015, 06:57:38 am
I'm working to get him and a couple of his friends from namecoin to join us in a Mumble hangout soon.  That is going on behind the scenes.  They seemed interested, so we it is more likely than not it will happen.  :)

Please PM me the day/time/timezone so I can listen in, thank you so much fuzzy :)
See our comments above this post too regarding squatting and icq-style app..
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 21, 2015, 07:58:49 am
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?
At any rate I asked @indolering to comment on this thread to give us an update about launching his delegates.

Maybe @indolering (or whoever) could use a combined set of DPOS and Open Transactions (OT) for this? Bitsapphire mentioned OT may be used as well.
The UN could issue an order to shut down all crypto related websites or web wallets tomorrow. 
 
Can we (doodle?) schedule a mumble with the key players for this and get some kind of roadmap for ddns?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: Thom on April 21, 2015, 04:42:38 pm
The UN could issue an order to shut down all crypto related websites or web wallets tomorrow. 

This is why I am so puzzled that DNS has been allowed to fall from our focus. This is not an impossible scenario by any stretch of the imagination, and I don't know why a sense of urgency isn't more prevalent.

Thanks again kenCode for resurrecting this in the consciousness of the community.

Thanks also to fuzzy for trying to make the hangout with indolering / NMC happen.

I read indolering's proposal, and it is obvious he is well studied on DNS & the institutions and politics involved with it. I would like to understand his perspective of trying to reshape those existing structures vs. inventing new, separate ones that obsolete the existing, in the same way as blockchain tech obsoletes existing financial infrastructures.

There are clearly challenges in making a pathway to bridge the old and new in DNS just as there are for crypto & fiat currency.

Perhaps I'm too much of an idealist. I get uneasy when proposed bridges feel to me as clinging to the old, or at least rely too much on the old, rather than blaze a new independent trail to reach the destination. I dislike methods that strengthen the old ways (or allow them to continue to live on) as justification for adoption of a proposed path to reach our destination, as a means to gain adoption of the new system, closer to the ideal which is free from coercion, manipulation and control by a centralized entity.

DNS is technically not that difficult of a problem to solve. The challenge primarily is political, practical and how to reach a consensus on the  approach to take, without compromising the goal of a solution that supports freedom.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 22, 2015, 07:03:34 am
Another major media Writer wants to do a story with me about BitShares DNS (ddns?) now and how it's coming along.
I told him that I'd get back to him asap.
 
@Indolering
@Toast
@Stan
@ByteMaster
@___________?
 
Guys please contact me about the DNS roadmap ASAP.
I don't want to lose the media momentum I am building.
 
Thanx in advance,
  -ken
 
ken@kenCode.de
Skype/Tweets: kenCode_de
G+ and Hangouts: http://google.com/+kenCode
 
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: xeroc on April 22, 2015, 07:45:25 am
I think DNS is on a hold until 1.0 release ..
lack of man power would be my guess
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 23, 2015, 05:34:42 pm
I've got a Dev connection at namecoin, will contact him now..
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: Akado on April 23, 2015, 05:59:05 pm
I've got a Dev connection at namecoin, will contact him now..

Are you thinking of making some kind of joint project with Namecoin? If not, then I would like to suggest so and even sharedrop to namecoin holders (i actually don't own any). DNS would get more support, BitShares would get more exposure and create a good relationship with a new community, which I think we are in need since apparently people see us as a community that bashes other projects and that's it, that we're arrogant. That would fit in nice and we would only win with that situation imo
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 23, 2015, 06:12:17 pm
I've got a Dev connection at namecoin, will contact him now..
Are you thinking of making some kind of joint project with Namecoin? If not, then I would like to suggest so and even sharedrop to namecoin holders (i actually don't own any). DNS would get more support, BitShares would get more exposure and create a good relationship with a new community, which I think we are in need since apparently people see us as a community that bashes other projects and that's it, that we're arrogant. That would fit in nice and we would only win with that situation imo

I'm all over it. 8)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: namjar on April 24, 2015, 07:56:21 am
I think you should contact EMC Dev (emercoin.com) to cooperate for decentralized DNS.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: Ander on April 24, 2015, 08:37:46 am
While I voted for after 1.0, there is nothing wrong with getting someone to work on it right away if that happens in parallel to 1.0.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 24, 2015, 08:48:24 am
I think you should contact EMC Dev (emercoin.com) to cooperate for decentralized DNS.

will do. i'll contact them as well. i am working with Bas over at NXT on this too. this joint deal will be huge for BitShares, watch me.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: Akado on April 24, 2015, 09:48:42 am
I think you should contact EMC Dev (emercoin.com) to cooperate for decentralized DNS.

will do. i'll contact them as well. i am working with Bas over at NXT on this too. this joint deal will be huge for BitShares, watch me.

btw, it seems emercoin is in need of an exchange  :P
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 24, 2015, 09:56:05 am
ok, ill discuss that with them as well. awaiting emc reply now. i have added this info to my delegate proposal, in the cointelegraph thread.
with emc, my decentralized dns working group, ddnswg, will consist of 5 companies and about 7 experts so far..
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 24, 2015, 11:21:16 am
spent some time on skype with Oleg today, he is very open to my ddns working group. he is the emercoin dns core developer and "tech lead". he has developed a very nice solution for the squatting issue too. he wrote an open api that our ddns model can work with. emercoin.com/EmerCoin_and_OpenSSH is also a great resource. he has registered about 200 domains so far on their blockchain. opennic is working with emc as well. once i speak a bit more with Bas over at NXT i think ill start putting all this into a spreadsheet in google docs that we can collab on. by working together on ddns, we all win. as usual, ill keep the BitShares community updated. sorry for my grammar here, on tablet while my crappy wallet pc is upgrading to 0.9.0.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: fav on April 24, 2015, 12:01:58 pm
spent some time on skype with Oleg today, he is very open to my ddns working group. he is the emercoin dns core developer and "tech lead". he has developed a very nice solution for the squatting issue too. he wrote an open api that our ddns model can work with. emercoin.com/EmerCoin_and_OpenSSH is also a great resource. he has registered about 200 domains so far on their blockchain. opennic is working with emc as well. once i speak a bit more with Bas over at NXT i think ill start putting all this into a spreadsheet in google docs that we can collab on. by working together on ddns, we all win. as usual, ill keep the BitShares community updated. sorry for my grammar here, on tablet while my crappy wallet pc is upgrading to 0.9.0.

 +5%

SuperDDNSNET incoming? :)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 24, 2015, 10:07:52 pm
It never hurts to ask, right?
 
Guys, I could really use your upvote on my comment here:
http://cointelegraph.com/news/114050/change-is-coming-how-the-blockchain-will-transform-the-domain-name-business#comment-1985672450
 
By upvoting my comment, please, it will help me to bring my DDNS Working Group (DDNSWG) to fruition for us.
Please and thanx :)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: crypto4ever on April 25, 2015, 04:37:37 am
Why don't we have a Bitshares forum devoted to DNS?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 25, 2015, 06:30:54 am
Yep, once I have the members assembled for the DDNSWG I will create a pinned thread (that hopefully I can Moderate), possibly in @gamey 's "Task Forces" section here:
 
https://bitsharestalk.org/index.php/board,70.0.html
 
Gamey expressed that he might be dumping it though, so we'll have to discuss it when that time comes.
 
There's also a wiki and press/PR sections where I may soon be maintaining threads.
I hope to be voted in as a Delegate so I can work full time BitShares.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 27, 2015, 03:18:04 pm
..yet another reason why my DDNSWG is so important:
http://www.coindesk.com/bitcoin-websites-fight-censorship-russian-court/
 
If we don't get DDNS in gear quick, the UN's Order to shut down ALL crypto wallet sites, etc. may come like a thief in the night.
Come on guys, give me your vote on the Poll up there, please.
 
imagine:
btsd:land.kencode.office.printer.queue("QUANTITY") or..
btsd:land.kencode.home.kitchen.oven("CURRENT_TEMP") or..
btsd:web.kencode or..
btsd:web.kencode.kontakt or..
btsd:web.kencode.projekte or..
btsd:mail.kencode or...
btsd:call.kencode
 
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 29, 2015, 09:47:42 am
@toast is the DDNS man among men, please don't misunderstand what I said above. I hope he can assist us with this.
 
I need all hands on deck for this DDNSWG. This massive project will fundamentally change everything we thought we knew we needed DNS to do -if that makes any sense :o
 
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: indolering on April 30, 2015, 08:07:44 pm
My apologies for being late to the discussion, I'm not much of a forum person and I didn't get an email from Ken until recently.  I'll try to explain what I can about the delays in tomorrow's hangout, but things are in full swing and we are working towards a viable decentralized domain name system.  However, I would love more smart people pitching in!

As far as what we need right now, the most important next step is a threshold signature scheme that can produce vanilla RSA signatures.  This allows us to build a system in which delegates can sign zone exports using DNSSEC.  This requires hiring a cryptographer/mathematician/programmer to implement a scheme outlined in academia (https://mega.co.nz/#!ZhYFBRxQ!fOGLMo7csQFcl9gqGtEvs6hGPG8-qY5bdMz0fJyG34I
Include file key) and it's what my delegate pay will be funding initially.

Browser add-ons and system level integration is another important step.  Namecoin's middleware, NMControl, is designed for this task and it will act as the backend for the browser OS level integrations.  NMControl is modular, the plan is to change the name and add BitShares support.  We also need to switch to Python 3, create a MITM-proxy plug-in, and port over Unbound.  If you are python programmer and interested in helping out, head over to the Github repo (https://github.com/namecoin/nmcontrol).

In terms of lightweight clients, BitShares has a long way to go.  Indeed, the primary reason for launching a DNS specific DAC is to improve the lightweight client situation.  The only thing that should be stored in the blockchain are public key fingerprints and nameservers, waiting ten minutes just isn't a big deal and bloats storage requirements.

But since DPoS embraces delegation of trust, I'm not sure it would be that much better than just relying on DNSSEC signed zone exports (and thus keeping everything within the BitShares blockchain).  The system works by having two keys, a Zone Signing Key (which signs zones) and a Key Signing Key (which signs the Zone Signing Key).  Delegates will sign zone files using the Zone Signing Key (ZSK).  If a certain threshold of delegates are proven to be producing incorrect zones, the KSK could sign a revocation of trust in the old ZSK and sign a new ZSK. Software trusting the KSK wouldn't need to be updated unless the blockchain chose a new KSK for some reason.  Even if a new KSK is needed, the new KSK can be signed by the old KSK, ensuring interoperability until software is updated.

Note that this is all threshold crypto, a certain number of delegates are required to produce a valid signature.  For the beta period, I think the KSK should be controlled by the developers and some mutually untrusted third parties in Iceland and other jurisdictions.  This is actually more robust than the system we have for signing the client software.  However, we could also setup a system for voting, similar to how delegates are voted in now.

So there you have it, I think that the important next steps are the RSA threshold scheme, upgrading NMControl, and a lot of political engagement and public relations work.

If you want to help out, start by hacking on NMControl and voting in my sec.indolering delegate!  After I get that one approved, I will pay the fee on the remaining delegates.

After my delegates get approved, I will post monthly updates and make an effort to visit the forum regularly.  You can also shoot me an email at zachlym@indolering.com.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on April 30, 2015, 08:21:43 pm
 +5% +5% +5% +5% +5%
I've got an army of Raspi's and BBB's on the ready.
We can PM again a good time to skype, I also would like to discuss the IoT ramifications of this.
And bring in a few other contacts I've made.
Thanx again Zach :)
Chat soon,
  -ken
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: Akado on May 06, 2015, 10:44:50 am
go for tesla http://cointelegraph.com/news/114149/adopting-the-chain-how-tesla-could-protect-its-website-and-its-cars
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 06, 2015, 10:48:24 am
go for tesla http://cointelegraph.com/news/114149/adopting-the-chain-how-tesla-could-protect-its-website-and-its-cars

Nice find Akado!
I'll use that thread, and put my two cents in there as well.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 06, 2015, 11:13:51 am
PLEASE UPVOTE THIS, IT BRINGS EXPOSURE & LEGITIMACY:
http://cointelegraph.com/news/114149/adopting-the-chain-how-tesla-could-protect-its-website-and-its-cars#comment-2008708292
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 09, 2015, 06:27:06 pm
Mike Ward, meet the BitShares community.
BitSharers, meet Mike Ward.
 
Mike Ward is a Technologist, Coder, and Writer for The CoinTelegraph amongst others. He's been following my comments regarding DDNS.
 
Mike I know you have some questions regarding DDNS and may like to discuss your past work in it as well.
So, without further ado, Mike you have the floor...
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: bitcoin42 on May 10, 2015, 04:52:06 am
Wow. This sounds amazing. All I was able to think of with this topic was this http://www.new-nations.net/
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: mdw on May 10, 2015, 06:07:23 pm
Thanks Ken. I think your thread here proves that interest in blockchain-based DNS is as strong as ever. There are many small missteps on the path, but the basic underlying need remains. There have been, and continue to be compelling reasons for decentralizing this core Internet infrastructure. Round up @toast and the gang and let's have some fun.

My personal belief is that Namecoin is going to really come into its own soon, after such a long period of stagnation. I also believe that other, different, blockchain-based DNS will come to market in quick succession, and mainstream folks will finally start to realize they have real choices. Maybe that'll include some offering from this group - I hope so. So count me in for whatever, I'll be glad to do what I can. - Mike
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: mdw on May 10, 2015, 07:11:07 pm
I think you should contact EMC Dev (emercoin.com) to cooperate for decentralized DNS.

Oleg from Emercoin is one smart and friendly guy, I interviewed him for a podcast a while back.
https://soundcloud.com/mightbemike/episode-01-oleg-khovayko - just past 15 minute mark

I'll ask him to check out this thread.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 10, 2015, 07:16:12 pm
Thanks Ken.
Maybe that'll include some offering from this group - I hope so. So count me in for whatever, I'll be glad to do what I can. - Mike

Thank you mdw, your vote of confidence helps my sanity, sincerely. Sometimes it just feels like people have their priorities all screwed up, like I'm the "chicken with his head cut off" as fuzzy put it. Our work here will be utilized by generations of people! :)
 
I've skyped with Oleg at Emercoin as well, he has some very intelligent things to contribute.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: mdw on May 11, 2015, 12:07:57 am
OK my $0.02 - for a Bitshares DNS offering, it's important to think up front about what the distinguishing features should be. My personal opinion is that the emphasis should be on the blockchain and DPoS. Domain Name resolution is the 800 pound gorilla, but it's a universal problem, and a proprietary solution from one chain will not satisfy the general need for all blockchain-based DNS. Be a different DDNS, highlight your inherent strengths through creative feature sets.

I would assert that since you have here a fundamentally different chain than Namecoin's "traditional-style" POW chain that should be the focus. Namecoin is very well served by the SHA-256 POW system they use, due to the unique merge-mining situation they have with Bitcoin. But making a weaker copy of that is, well, weak. Bitshares is a very fast, efficient chain with a different consensus model and should leverage that.

You have the potential here, for example, to get a new domain name registration up and resolving before even the first block is added in a 10-minute block system! Contrast that with Namecoin, where not only does each block take a while, but new registration requires two consecutive operations, so realistically you can't expect your name to resolve for people an hour after registering it.

Feel free to flame me to death for this next part, but I also believe that the emphasis on a complicated auction-style system to deter squatting was ill-advised. Not having a predictable annual cost is a negative for the business community, and I believe that "squatting", however you define it, is not an actual problem.

I've been involved in the domain industry for years, and people have complained since the late 90's that .COM was so completely squatted. Yet they continue tor register them, instead of going for shorter .WHATEVER domains. People find names, and the business has continued to boom with xxx,xxx,xxx .COM registrations. It continues to grow even this year, with hundreds of new TLDs introduced.

I don't expect many to agree about squatting being a fictitious problem, but my point is that designing feature sets around those capabilities that are unique to Bitshares chain is more appealing, no? You might prefer to think of it in terms of being a competitive advantage.

Near-instant registrations, as I alluded to earlier, would seem to be one such interesting differentiator. Ever look at Dash's (was Darkcoin) InstantX payments, where it happens almost immediately? This, for domain registrations (and subsequent website setup) is a killer feature that's very tough to match by any would-be competitors.

Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: .yoshi on May 11, 2015, 03:50:51 am
solid insights mdw. I think you're absolutely right;  no need to waste time and resources at this point over-architecting the product over potential non-issues. even if domain-squatting does become a problem it can probably be dealt with down the road.

build the mvp leveraging our existing strengths and improve it as we go along. just my .02 bts
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: pc on May 11, 2015, 07:31:47 am
but I also believe that the emphasis on a complicated auction-style system to deter squatting was ill-advised. Not having a predictable annual cost is a negative for the business community,

+1
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 11, 2015, 12:31:14 pm
@.yoshi
It's less expensive to code in the squatstop(first!) now. Not only that, but once mass-adoption begins, then we are barraged with people saying how we fucked it up, we didn't even try to stop squatters, etc. The labor to defend a short sighted decision is more intensive than if we had just took an extra day or week to figure it out now and code it in from the beginning.
 
@mdw
Here in Germany, businesses rely on their family name. Your name is everything here. In America, brands are used more than anything. Both can be seen as one in the same however, if you are Apple, then you want ddns:web.apple right? If squatters can snag it, how much more strife is created then? A lot.
 
Code it correctly the first time.
I'm hoping Mike Ward will chime in here, I got another email from him just now so will try to get his thoughts publicized in here as well.
 
Thank you everyone for your input on this! Our collaboration on this will be world changing :)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: mdw on May 11, 2015, 04:34:45 pm
Yes, I am Mike Ward. One of many, and I hope to get my name registered before others do! I missed mikeward.com by only a few weeks back in the 1990s, and the registrant of the same name has never let it expire :)

I didn't want to make too big a deal out of that point about squatting, except to suggest that whatever you consider it to be (and definitions vary) there are easy ways to mitigate it to some extent. Main point was supposed to be that choosing the anti-squatting mechanism as the feature to distinguish this product from others does not provide incentive to the people registering the names. Again, people have long complained that all the .COMs are taken, then they proceed to register one anyway.

Unique features like "instant registration" will make this more competitive IMHO. Better anti-squatting measures, not so much.

There are plenty of good ideas about how to mitigate the big land grab that takes place if you offer all-you-can-reg domains for dirt cheap. Registry operators in the existing system are a good model to look at. They typically hold back the best names, and auction them off later, after the value has (hopefully) appreciated. People taking registered service marks like "Apple" is a slightly different issue, and is traditionally dealt with by offering pre-launch sunrise periods, where trademark holders can get first rights to register, as well as a binding arbitration process to challenge "bad faith" registrations. They work somewhat, but not so great, for various reasons.

Holding back some names from general registration is an easy way to avoid most issues. Specifically for dealing with bulk registrations (like registering loads of common surnames)
And so on. There are probably as many ways to disincentivize bulk registrations as there are users on the forum. Some are easy to implement and fairly effective. :o
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 11, 2015, 04:56:20 pm
Yes, I am Mike Ward. One of many, and I hope to get my name registered before others do! I missed mikeward.com by only a few weeks back in the 1990s, and the registrant of the same name has never let it expire :)

I didn't want to make too big a deal out of that point about squatting, except to suggest that whatever you consider it to be (and definitions vary) there are easy ways to mitigate it to some extent. Main point was supposed to be that choosing the anti-squatting mechanism as the feature to distinguish this product from others does not provide incentive to the people registering the names. Again, people have long complained that all the .COMs are taken, then they proceed to register one anyway.

Unique features like "instant registration" will make this more competitive IMHO. Better anti-squatting measures, not so much.

There are plenty of good ideas about how to mitigate the big land grab that takes place if you offer all-you-can-reg domains for dirt cheap. Registry operators in the existing system are a good model to look at. They typically hold back the best names, and auction them off later, after the value has (hopefully) appreciated. People taking registered service marks like "Apple" is a slightly different issue, and is traditionally dealt with by offering pre-launch sunrise periods, where trademark holders can get first rights to register, as well as a binding arbitration process to challenge "bad faith" registrations. They work somewhat, but not so great, for various reasons.

Holding back some names from general registration is an easy way to avoid most issues. Specifically for dealing with bulk registrations (like registering loads of common surnames)
  • diminishing registration prices over an extended launch period help curb excess registrations,
  • higher renewal fees discourage holding large numbers of names over time waiting for high resale prices
  • requiring a certain amount of assets to be deposited or kept in an unspendable state for each domain registered might help (?)
  • perhaps only the first "premium" domain name registration per user account is cheap (where premium is defined in some arbitrary way like length of string < 5 characters and it's not on reserved list) For strings beyond that length, no limit, but more premium strings cost more and more.
And so on. There are probably as many ways to disincentivize bulk registrations as there are users on the forum. Some are easy to implement and fairly effective. :o

Aah cool, thanx Mike :)
MikeWard.com - seized by yet another squatter. You feel the pain more than I do then, having someone actually take your name.
 
I think the people that the squatters will annoy the most will be the larger brands and names, the ones especially that want to display their name on some form of advertising, like a tv commercial. Their domain has to be short and sweet. Like ddns:web.mdw
 
If registered on the BitShares blockchain, I can forsee names being snagged in 10 seconds flat (our block times). In the OP, I mentioned too that there could be a consensus mech involved where the LESS people that vote for you, the more expensive your reg will be. The land grab you mentioned. Domains, userid's, electrical outlets, light switches, aircraft and vehicles of all kinds. They should be routable and nameable too IMO. I think the "bad faith" you mention could be mitigated with that after-the-buy consensus vote.
 
Registering loads of names, that's a squatter. I can't see any reason why one person would want to register more than a few "TLD's", ie:
ddns:web.mdw
ddns:mail.mdw
ddns:land.mdw.home.oven (see this stuff above)
fact is, mdw becomes your new TLD for everything. Then it just child-nodes down from there.
 
I like your fee structure above. It becomes increasingly expensive for each new "TLD" the user wants to register.
 
What do you think of my list of names above? Toast, Vitalik, You, Oleg... Once we get our list of names picked out (kinda like the list used in the movie "Gone in 60 seconds) then we just need to schedule the g+ hangout, write the roadmap, get the project funded and knock it out.
 
Thanx for joining us Mike! :)
  -ken
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: Pheonike on May 11, 2015, 05:01:27 pm


The idea of a retainer fee on registering is good. You have to lock away a certain amount for a set period of time before it is released minus the normal registration fee. If a rights holder challenges and win, you lose the retainer.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: hadrian on May 11, 2015, 05:40:41 pm
I posted a topic - "Ideas for an alternative DNS model" (https://bitsharestalk.org/index.php/topic,9346.msg121000.html#msg121000)- a while back.
It didn't get any comments, so it's probably crap, but someone may find something of value hidden in there?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 11, 2015, 07:55:56 pm
@mdw
This very detailed post by @hadrian is nice, it mentions the leasing thing too:
https://bitsharestalk.org/index.php/topic,9346.0.html
 
Squatters get dealt with. This is one of the nicest writeups I've read so far.
This entire thread and everyone's ideas will be taken into consideration for the DDNSWG roadmap.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: indolering on May 13, 2015, 06:22:31 pm
Hey Mike!  Glad to see you are hanging around here still!

I won't address everything raised in the thread but I'll hit the highlights. 

Two hours vs twenty seconds for domain registration isn't a big deal: in my experience, it takes that long for resolvers to warm up and get things pointing to your host with traditional domains.  Just to be clear, you can't steal a Namecoin domain by simply rebroadcasting the initial registration info or even figure out what domain was registered based on the initial registration. You are left with the same race conditions that are true of two traditional registrars registering the same domain at the same time.

When it comes to fighting squatting, the goal is simple: reduce the profits of professional squatters.  There are various schemes for fighting them and they could all be benchmarked to see which ones impact squatters more than regular users.  However, outside of the initial "sunrise" auction, I think that auctions and complex pricing algorithms would just deter regular consumers. The range of prices is pretty narrow and dictated by competition with other TLDs: anything less than $5 is too low and anything greater than $50 is too high.

I strongly disagree with mechanisms that attempt to extract higher rents from established (legitimate) domains because these domains increase the overall value of the naming system (http://www.indolering.com/domain-name-squatters)   Any system that extracts additional rent from regular users will push them to TLDs that don't have exotic pricing schemes.

It's also fairly easy to foil algorithms designed to punish bulk domain purchasers.  For example, you couldn't increase the price for accounts with large numbers of domains beyond the cost of creating a new account.  Trying to setup delegates who decide what domains are being squatted on would just kick-start an unprofitable game of cat-and-mouse. 

And, again, the range of prices we can charge is very limited.  What's the difference between charging $25 per domain vs $5 + a $20 deposit?  The fact-of-the-matter is that we don't have enough money to pay someone to even implement such a scheme.  I would prefer to just set prices at $20 and mess around with pricing algorithms after we get off-the-ground.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: mdw on May 13, 2015, 07:27:30 pm
Hey Indo  :)

Great comments, and no, we'll never have a consensus about "squatting," whatever that means to the individual reader. Your view and mine are closer than most I think. There are multiple behaviors that always seem to get lumped into this generic bag called squatting. They should be dealt with differently, as they are in the conventional system. How much of a problem the respective behaviors are is a matter of opinion, but each has its unique set of edge cases to be accounted for.

As for fighting "squatting" I personally don't think any of this is necessary. I think the only thing that *should* be done is to hold back the best names, as the conventional registry operators do. Not to prevent them from being registered, but simply because a lot of money can be made selling them for high prices. But almost everyone here disagrees, and thinks squatting is a huge problem, so I simply wanted to say that there are so many easy things you can do to make it less desirable.

My point about the speedy registration times was that it's a distinguishing feature Bitshares can offer that competitors cannot. The original project had the "anti-squatting" mechanism (auctions) touted as the primary thing that was different. So I tried to make the point that offering "instant registrations" is a better differentiator. First time registrants are often eager to get started. And paired with some really basic DIY web page builder they can register a name and have a simple site built and resolving in minutes. Not hours. No other potential competitor can offer this to my knowledge.

This chain is fast, and that fact should be exploited. Play the cards you're dealt right? It's also more centralized, and I think that can be used to great advantage in designing certain system features as well.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 27, 2015, 09:01:21 am
If they can't seize your crypto directly, maybe they could even block wallet apps. Related:
http://www.coindesk.com/accenture-uk-government-should-regulate-bitcoin-wallets/
 
Next, banksters/govs will backdoor us by shaking hands with the UN and ISP's.
 
Question:
DDNS is one thing, but is it possible for ISP's (or phone malware they inject) to block which types of apps you can download too?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: xeroc on May 27, 2015, 09:34:10 am
If they can't seize your crypto directly, maybe they could even block wallet apps. Related:
http://www.coindesk.com/accenture-uk-government-should-regulate-bitcoin-wallets/
There's a big fact "SHOULD" in the title .. it doesn't say that it is possible

Quote
Next, banksters/govs will backdoor us by shaking hands with the UN and ISP's.
Governments already shake hands with ISPs and the UN is defines a "united" set of governments

Quote
Question:
DDNS is one thing, but is it possible for ISP's (or phone malware they inject) to block which types of apps you can download too?
if I understand you right then what you fear is technically not possible
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 27, 2015, 10:37:55 am
if I understand you right then what you fear is technically not possible

Could Moonstone be blocked via dns?
Or via a specific port that's used by Moonstone?
Maybe the type of technology/protocol/algo the wallet calls on?
Or its particular app name?
Or where it is downloaded *from*?
Or keywords it uses upon execution?
 
I'm not an ISP, but I can foresee them already thinking this stuff through. If they were ordered to stop the Lime Wallet, Mycelium, Moonstone (or what have you), these (above) may be some ways they could give it a shot, no?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: xeroc on May 27, 2015, 11:01:55 am
Could Moonstone be blocked via dns?
Sure .. but you can also host moonstone on your own hardware .. elsewhere .. see
thepiratebay

Quote
Or via a specific port that's used by Moonstone?
Maybe the type of technology/protocol/algo the wallet calls on?
sure .. it's tcpip/http/www .. I my ISP was to block those I take legal actions

Quote
Or its particular app name?
Or where it is downloaded *from*?
Or keywords it uses upon execution?
??? Makes no sense .. names can be changed .. download sources too
 
Quote
I'm not an ISP, but I can foresee them already thinking this stuff through. If
they were ordered to stop the Lime Wallet, Mycelium, Moonstone (or what have
you), these (above) may be some ways they could give it a shot, no?
At least in Germany there exists software that is illegal to use (though not to
download) .. those are called "hacker tools" or more technically "penetration
testing software" ..

Let's see what action legislation might take .. at least for bitcoin you seem
to be rather safe .. in Germany .. it is totally allowed to use here

How about do some research first and no spread FUD?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 27, 2015, 11:41:27 am
Let's see what action legislation might take .. at least for bitcoin you seem
to be rather safe .. in Germany .. it is totally allowed to use here
How about do some research first and no spread FUD?

What's FUD?
These questions *are* legitimate research.
 
As for legislation, IMO it doesn't matter who, or what you vote for anymore. When the populace is overrun by sheep that have been beat down their entire lives, they get excited when they see others persecution and support it wholeheartedly. Sad. That's the kind of stuff that will end these projects.

Here's some more "research":
What if the ISP's just disallow you to download an app called "xeroc"? That's what I meant by "name" earlier.
China blocks access to facebook, right? Why not all crypto web/appstore/gplay wallets too? Do you understand my concerns?
How about the ISP just blocks all of your encrypted packets?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: crypto4ever on May 28, 2015, 11:09:19 pm
Decentralized DNS must allow a registered host to "Network Hop" and update the blockchain continually.

Currently authoritative DNS for a domain typically exists for 259200 seconds (3 days)

I don't know what design will happen for decentralized DNS, but I should be able to be www.somesite.php = 192.168.1.1 in the morning, and then I can be www.somesite.php=192.168.2.2 a few hours later.

If you're going to use authoritative dns servers (like ns.somesite.php and ns2.somesite.php, those must be able to be changed hourly (or by the minute) too)

Finally, the "history" of what IP's a p2p site or its authoritative dns was a few weeks ago, should be irrelevant, so a new user downloading the chain doesn't need to know where the site was in the past. It only needs to know the latest information about where the site is "right now"

You will find that IP changes and network hopping will be common once p2p goes live. 

By the way ever see the Leonardo DiCaprio movie "Catch me if you can?"   - We all know who will be filling the same role of Tom Hanks in that film, in a p2p DNS environment.

Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: crypto4ever on May 28, 2015, 11:17:04 pm
When the populace is overrun by sheep that have been beat down their entire lives, they get excited when they see others persecution and support it wholeheartedly. Sad.

This is why people laugh hysterically when a cop pulls over a speeder in  front of them. Baha haha he deserved it! I hope the cop gets him good! They cheer.

Little did they know they speeder had his dying 9 year old daughter in the backseat with her mother holding her, while they were on the way to the hospital. Yes, the daughter just got hit while he was changing a tire at the side of the road and there was no time to wait for an ambulance.

Yeah, you never know what you're maniacally laughing at when you see the persecution of somebody else.

What I think it amounts to is relief in the form of laughter, like, "finally! some else has their day ruined instead of just me"

We all have sick habits that need to be corrected.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on May 29, 2015, 07:57:13 am
Excellent, educated, insightful replies crypto4ever, very refreshing thank you :)
 
I guess most people are just not thinking yet about how important DDNS really is.
We work so hard to get decentralization to the masses and bring an end to corruption, poverty, haters, etc that we lose focus. The speeder issue you mentioned was right on target for most people, I'm sure. When I see police questioning people however, I have a completely different reaction. I see government using force to get you to comply with whatever their latest demand is. Most people don't even know their rights. Yes, fighting the system can get you into heaps of trouble (I should know) but when we stop trying, we lose. Bigtime.
 
All of our efforts are probably being laughed at right now by our "leaders" because they know that all they have to do is order the ISP's to start locking it down (via the many methods I have mentioned in my posts). It's sad, I'd hate to see all of our work go to waste.
 
If they control the internet, they control it all. Just like food, energy and money.
 
Ok, back on track, this thread is supposed to be DDNS related hehe :)
@crypto4ever - Would you like to participate in one of our DDNSWG Panels on mumble?
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: hodor on May 29, 2015, 11:52:22 am
Hodor!
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on July 01, 2015, 11:28:03 am
Looks like we're not the only ones working on DDNS:
http://what3words.com/examples/
 
EuroNews just had a segment on it:
http://www.euronews.com/2015/06/29/new-app-puts-everyone-on-the-map/
 
I foresee more than 3 words (ddns:mail.kencode, ddns:web.kencode, ddns:temp.oven.kitchen.home.kencode, etc), but they are doing exactly what I said was going to be needed for routing to an address or device. Let's decentralize everything! 8)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: emigalotti on July 14, 2015, 02:52:09 am
Looks like we're not the only ones working on DDNS:
http://what3words.com/examples/
There are a lot of people working on DDNS, I know a couple.
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: kenCode on July 14, 2015, 07:16:50 am
If it's ok with them, maybe you could PM their contact info to me so I can chat with them about it?
Thanx so much @emigalotti :)
Title: Re: BTS: .P2P .DAC - Decentralized DNS using the BitShares blockchain!
Post by: cass on July 14, 2015, 07:57:23 am
If it's ok with them, maybe you could PM their contact info to me so I can chat with them about it?
Thanx so much @emigalotti :)

or jsut invite them to our community here ... so we can start a public discussion :)
This would be great...