Topic: [ANN] SuperNET NXT asset 12071612744977229797, SUPERNET KMD assetchain in summer - page 119. (Read 736806 times)

The tech is still being worked on diligently.  SuperNET asset holders have gotten a couple of nice dividends so far (NeoDICE and NXTinspect).  For a good summary of what's been going on, you can read through the SuperNET newsletters:  https://forum.thesupernet.org/index.php?board=37.0

Also, all important updates and happenings seem to have been moved over to the official superNET forum.  So it would be inaccurate to judge superNET based on things posted here.  The newsletters are probably the best source of information as of now. 

Has SuperNET actually produced anything yet or still vapor?  I'm not reading through 200 pages and the OP really needs some work...makes SuperNET look scammy...

Has SuperNET actually produced anything yet or still vapor?  I'm not reading through 200 pages and the OP really needs some work...makes SuperNET look scammy...

Thanks for your support!
I am not a cryptographer, but I do have a knack for doing creating things with existing tools.

The whole deaddrop routing I think is quite significant as I cant figure out how it can be attacked. once the network gets a critical mass of activity, it will look like everybody is sending to everybody, which is the same as nobody sending anything. As close to white noise as can be.

I am having cassius write up a paper to explain the whole deaddrop method using DHT and n-space equidistant addresses

James

Hello everyone
I have started a SuperNET API documentation thread here: https://forum.thesupernet.org/index.php?board=41.0
I have begun populating it, though am still wrestling a little with the installation and update process myself. If anyone gets an automated process up and running - Linux or Windows - that would be fantastic and would no doubt enable many more people to do some testing and experimenting with it. Remember: James has offered a 1,000 BTCD bounty if you can find a way to break it...
I will be taking a little break from this for a while to get my head around DHT routing and N-dimensional space equidistant addresses and write up James' new plan to send messages to people without even knowing their IP address. 'Imagine being able to send email to someone without knowing their email address and without spamming everyone. This is on that level of crazy.'
Assuming I survive this, I'll get back to the API documentation afterwards. In the meantime, please feel free to add material to the documentation threads above. When I get back from my trip to N-space I'll incorporate any new information into the OPs.

Thanks for your support!
I am not a cryptographer, but I do have a knack for doing creating things with existing tools.

The whole deaddrop routing I think is quite significant as I cant figure out how it can be attacked. once the network gets a critical mass of activity, it will look like everybody is sending to everybody, which is the same as nobody sending anything. As close to white noise as can be.

I am having cassius write up a paper to explain the whole deaddrop method using DHT and n-space equidistant addresses

James

Hi James,

Thanks for creating the superNET and teleport.

SuperNET and teleport are both very unique and exceptional project .

Your name will be recorded in the history of cryptography sciences  .

I concentrate on increasing the value. The price, it goes up and down and cant be directly controlled. however, by creating more and more tech which can be used to create more and more useful end user solutions, the value of SuperNET will continue to grow. The price will oscillate around the value

James

Are you going to be looking for people to contribute hardware/bandwidth for masternodes?

running some simulations and when we get to ~500 nodes, within a few minutes I am finding a deaddrop address that has the exact distance to ~20 nodes. this is at distance 24, which I believe is about 1/256 of total nodes and with a K factor of 7 even without any special relaxing of distance requirements, the packets will automatically arrive at your IP

Thanks for the updates James. Really excited to see SuperNET in action! I assume the price will jump quite a bit once people see it working and in the wild.

RESERVESHARE
@Jl777News is a follower of the twitter @reserveshare



Between yesterday and today massive selling has taken place, that joined the absence of news on the part of the dev, they do that we do not know exactly that it happens with the AE called RSUnit.

The price of the AE RSUnit has fallen down in 2 days from 1 up to 0.02 of now.(-98 %)

A clarification would be interesting on the part of Supernet, as for relation that joins her at present with Reserveshare, to prevent the people from coming to buy seeing that Supernet is a follower of Reserveshare.

If there is relation, already to communicate it and if it is not, it would be suitable that they were withdrawing the pursuit in Twitter so that the people do not take to trick and we could lose more than in this moment we are losing.

https://bitcointalksearch.org/topic/m.9174887

I pushed a new version with findaddress API

./b SuperNET '{"requestType":"findaddress","refaddr":"8894667849638377372","dist":24,"numthreads":20,"duration":6000,"list":["13434315136155299987","8894667849638377372","10694781281555936856","18429876966171494368","16163006958863727986","1838354277347686608","17572279667799017517","14815310753561302584"]}'

The refaddr is your privacyServer's NXT address, dist is the distance in bits (after xor), numthreads is the number of parallel tasks doing the search, duration is in seconds and list is the reference list of public server addressees

This will run in the background until the time runs out and it will print out a password and stats for your super private account. I havent done the storing in encrypted file or anything else yet. while it is running, if it finds a better acct, it will print:

>>>>>>>>>>>>>>> new best (super secret password) ...

so you can always search for this and get decent accounts to use while the findaddress keeps working in the background. It is kind of like mining! But what it is doing is actually very useful. It is finding the perfect address for you to use by making it look like an address that could be linked to any of the other public servers.

Due to the way the accounts are created, bruteforce random guessing is the best way to find such an address. This is a good thing as it means that the encryption is quite good. After all if the distance between the mined acct and the reference account went to zero, we have effectively hacked it!

The search is creating an N dimensional space where each dimension is the distance from one of the server accts in the list. The metric function is a bit more complicated, but conceptually we want a point in N-space that is equidistant from as many public nodes as possible. With the current number of nodes being so small, it is hard to come up with any address that meets this criteria, but at a distance of 24, given enough time, it should be possible to find an address that is +/- 3 distance from most of the list.

I am hoping that with more nodes, it will be possible to find addresses that are around 20 bits distant and still have the above characteristic.

Now why on earth do we care about such things?

The reason is that this solves the "last mile" problem of how to establish totally private comms without resorting to broadcasting to everybody. My coding the DHT is what allowed me to solve this, so those that think these seemingly unrelated things are slowing down the progress, it is quite the opposite. It is helping achieve the ultimate goal!

To understand how this allow comms without divulging the IP address, requires a bit of background on DHT, especially the Kademlia XOR distance method. Using XOR as a distance function sounds so simple, but it has some very powerful mathematical properties. Namely, you can know if another node is closer or farther away from the desired location, totally in the abstract. Imagine that you start searching for something. It gets a delivery address (in the abstract not IP). Now you find all the nodes you know about that are closest to this address and ask them to deliver it. You only know they are closer to the destination that you are.

That's it!

Of course a lot more details, but this is emergent behavior, eg. out of very simple behavior at the local level, some powerful global functionality emerges. Imagine you got the packet from someone that was farther away than you are. Now you do the same thing and the packet keeps getting closer and closer to the destination. Finally it gets to the nodes that are as close as possible that are in the network.

All the SuperNET nodes are part of this "bucket brigade", each passing the packet one step closer to the destination. This means that your node is also going to be involved in this and everybody knows your public server's acct and IP address. If not because you publish it, but if they wanted to the attacker can do sybil attacks and get this info. It is simply unavoidable to get an account linked to the IP address if you are transacting with it.

However, we have the private address that only people you transact with know. Your privacyServer's acct is known along with its IP address, but as long as you are careful with who finds out your privateaddress, then it is just an address that happens to be equidistant from N other privacy servers. Which one? Could be any of them as the way the DHT works is that it replicates the info to all the nodes closest to the destination, which in this case is your address. Taking advantage of this property of the DHT and the fact that your privacyServer will be handling the routing allows packets that are encrypted to your private address to be received by your computer and you can decrypt it as it is sent on to the closer nodes.

As the network grows, it will become harder and harder even to identify the set of possible nodes your private address belongs to. So even if your private address is compromised, there isnt a way to link it to any IP address!

James