IPv6 is already being deployed from top tier mobile carriers and that allows globally rout-able addresses even behind NATs.
"That doesn't inspire much confidence in the idea as a proof of concept."
This technology is a little ahead of its time, but not by much. And by the time an end-user ready core is developed, we'll we be there.
"Are you sure you're able to make that claim?"
yes, the technical hurdles are only time consuming, not insurmountable.
With all due respect, if your solution depends on the following developments in the real-world:
(1) Everyone upgrades their cheap DSL/cable home modems to something that supports IPv6 (2) Cell carriers allow incoming mobile data connections (can you say mobile DoS?) (3) People modify their firewalls (again, nothing to do with IPv4 or IPv6) to allow incoming connections (4) You devise some way of allowing static or otherwise identifiable IPv6 IPs, even when the ISP doesn't give you a static IPv6 IP
then I would say you have a number of challenges ahead of you. Assuming that device X and connect to device Y on the Internet, for consumer devices, is a very difficult proposition.
[citation needed]
All of them (to my knowledge, and yes, I've researched this) still require some sort of central network that gets contacted first. "Trackerless" bit torrent, for example, uses a DHT that is hosted by... bittorrent.com
With all due respect, based on your posts your current understanding of how things like Skype and Bittorrent operate under the hood in a "server-less" environment has a few holes.
http://en.wikipedia.org/wiki/Distributed_hash_table
http://en.wikipedia.org/wiki/Local_Peer_Discovery
1. A requirement seems to be the ability to make and receive socket connections. How would you address the typically restrictive home firewalls/NATs that most people are living with?
2. In the responses, a commenter raises this issue: With the above example of two users and 56 connections it seems like there could be scaling issues and or perormance issues. They may be less obvious on computers but mobile devices with more limited bandwidth and sometimes quotas may suffer for those users with muilple devices and their multi device highly connected friends.
The response from admin is: "Correct, this technology will have to scale along with hardware. I don’t believe we are too far off with 4g, more inexpensive memory and the like."
That doesn't inspire much confidence in the idea as a proof of concept.
You're also claiming to solve a far more fundamental problem: that of creating and maintaining a reliable distributed peer-to-peer network without any central servers at all. If you do have a practical solution to this problem, then a bunch of other difficult problems (like tracker-less Bittorent, for example, which currently relies on distributed hash tables) reduce to yours. Are you sure you're able to make that claim?