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

Now, time for lunch and then I can put this all together and get a Telepathy demo

James

To prevent the spoofing, I added a contacts list:

SuperNET '{"requestType":"addcontact","handle":"jl777","acct":"NXT-P3K3-M9XB-5MDG-DVNT8"}'
SuperNET '{"requestType":"removecontact","handle":"jl777"}'
SuperNET '{"requestType":"dispcontact","handle":"jl777"}'
SuperNET '{"requestType":"dispcontact","handle":"myhandle"}'

These are basically a way of mapping long acct numbers to easy to remember handles for use in other API calls. Nothing fancy. Since they are not stored on HDD you need to put a "contacts":[{"jl777":""}....] field in SuperNET.conf or have the GUI do it on startup.

calling addcontact again will just update the acct. These accts have to be funded with at least 1 NXT I will add a display handle API with a special handle called "me" that shows your private acct and public key.

There is a special handle "myhandle", which is set to your pubaddr -> NXT numerical address -> reed solomon RS address. This is so you can let others know what address to set your handle to.

Also if you dispcontact "*" it will return all contacts

These API should allow a contacts GUI to be built

James

P.S. As the observant have observed, using handles -> accts allows us to generated a shared secret based on the public key of the acct and this lets us use the cloud using a location that nobody else will be able to find, at least not without a brute force search and we also skip a step as the public key can be used to exchange Telepathy addresses and this also gets us non-realtime transactions! Not bad for such a simple API 

./BitcoinDarkd SuperNET '{"requestType":"getpeers"}'

without SuperNET.conf it wont connect to the Supernetwork

I think I might have just fired up a node.    I was supposed to make a config file somewhere but it seems as if its running.  How can we all see nodes on the network?

Well we are dam lucky that James isn't the average Dev

Jon 

The SuperNET and JL777's Effect.

The more I monitor the development of SuperNet and potential alt tech coins participation, the more I am reminded that the average person who "devs" an alt coin A) isn't that bright B) isn't that old/experienced C) isn't that bright (oops did I mention that already?) D) is greedy and E) lacks any real vision or ingenuity.

##supernet on freenode.

Right lads, I have rented a server on Digital Ocean for an indefinite period of time.  I want to add to the network, where's this Digital Ocean guide I saw a while back?  Is there an IRC channel I can dip into if I get stuck?

we were in discussions and then all of a sudden no contact

now I know why. it was probably just competitive intelligence gathering, or maybe just coincidence that days after contact is broken off, the blocknet is announced.

my interest in NHZ was their 3000 nodes, while this is not in and of itself a technical feature, it does have tangible value. The fact that the XC dev is also advising NHZ makes all this very coincidental and leaves me feeling not so good about the NHZ guy either. If they wanted to find out about SuperNET, why pretend about being interested in a deal?

Anyway, NHZ is a clone, so it makes sense for it to become part of the cloneNET blocknet.

James

no i am very curious. are you trying to suggest here that NHZ is supposed to be added as a core coin of supernet or at least going to be somehow related to it? or what do you exactly mean with "promising discussions with NHZ"?

So they're basically saying:  "Pay us to copy SuperNET".  Sure sounds legit.  I'll be watching this closely.  Very curious how their ICO will turn out.

It is quite similar indeed, even down to doing an ICO with discounts for the coins.
Interesting thing is that I was in promising discussions with NHZ and they have some common people with XC

The graphics they have done are pretty good, and they are explaining SuperNET quite well, even down to the usage of JSON for the RPC. I also see some coins on their list that we did not accept, but as a clone they have to have lower standards.

It will be interesting to see if a SuperNET without any financial feedback will be possible. My opinion is that it takes energy to bind disparate coins together and revenue sharing, co-investment are critical parts of the SuperNET concept.

Also, it is not clear what they will do with the funds raised.

James

Found it:
"The Blocknet Foundation will pool the formidable abilities of developers and will function
as an incubator, funding the creation of a development platform and multiple Blockchain
2.0 services. The Foundation will be responsible for allocating funding for this."

So their fund raising is going to pay for development of their SuperNET clone and not be backing the asset at all. I wonder if the trolls will be making any issues about buywalls?

Do you think the upcoming "Blocknet" ICO will be a significant competitor to SuperNET? The Blocknet is an inter-blockchain application platform enabling each coin to serve every coin. This feature sounds somewhat similar to SuperNET. More precise detail can be found via the referenced links below.
References:
https://bitcointalksearch.org/topic/m.9216584
http://downloads.xc-official.com/images/14-10-15%20Blocknet%20presentation.pdf

LOL + 1000 superNET dividends

What a completely ridiculous statement.  You want to talk about something that looks scammy, checkout MaidSafe or Ethereum.

   You finish the task, can go home. Taking profits, making the waiting.

after doing the following API (one on each computer):
./BitcoinDarkd SuperNET '{"requestType":"mindmeld","myname":"yourhandle","other":"otherhandle"}'
./BitcoinDarkd SuperNET '{"requestType":"mindmeld","myname":"otherhandle","other":"yourhandle"}'

The following happens:

38 28 33 33 40
28 32 31 27 28
33 31 29 32 35
33 27 32 33 31
40 28 35 31 30
dist from privateaddr above -> bestmetric 0.632 avedist 31.8
31 28 33 33 40
28 31 31 27 28
33 31 30 32 35
33 27 32 32 31
40 28 35 31 31
bestaddr.3397518935526591714 bestmetric 0.632
Other pubkey.(c330e6542defef123504ebe247603008df234859ee55225d1124534462436b1b)
10694781281555936856 8894667849638377372 13434315136155299987 17572279667799017517 18429876966171494368 mytxid.7232362215934077752 othertxid.6762902089573300365 | myaddr.2834459742776037913

############# other node

28 31 28 27 28
31 35 33 32 35
28 33 40 33 40
27 32 33 35 31
28 35 40 31 34
dist from privateaddr above -> bestmetric 0.632 avedist 31.8
31 31 28 27 28
31 32 33 32 35
28 33 31 33 40
27 32 33 30 31
28 35 40 31 31
bestaddr.7112391407263245770 bestmetric 0.632
Other pubkey.(ffe89032a5d457014b02c704a7b19eede4cfce1fc83fa554f0e875098d06240f)
8894667849638377372 13434315136155299987 10694781281555936856 17572279667799017517 18429876966171494368 mytxid.6762902089573300365 othertxid.7232362215934077752 | myaddr.5558871420373351853

I am displaying the distance from the actual private address (red) in the top matrix and the distance from the deaddrop address (blue) in the bottom matrix. In DHT the distance is really the only useful information about an address. The red address is NEVER sent publicly, only the publickey is put into the cloud in a location based on the handles the two people use, so it is "published" as anybody can access them, but generally public keys are public so this is much less info than normal.

Once both sides exchange public keys, they then can encrypt and only then are the deaddrop addresses exchanged. Notice the difference in the account numbers red vs blue. what is more important is that the distance of the blue addresses from the other nodes:

31 31 30 32 31
31 32 31 30 31
 
as opposed to the red addresses:

38 32 29 33 30
28 35 40 35 34

Keep in mind the average distance is 31.8, so let us assume that someone the blue address is compromised. What does it divulge?

It is pretty much equal distance from all the other nodes (including the actual source and destination), so it is like camouflauge. Even if the attacker got the blue address, it certainly cant lead to the red address and it just ends up saying equal chance for any of the nodes to be yours, basically useless guessing. As the network grows, the effect becomes stronger, though finding addresses that are equidistant from a large number of addresses becomes more and more difficult so there will be an eventual cap on the anon set from this.

Notice that not only is the IP address not known, but the destination acct address is not known either, in fact there is no actual destination account, that is how I know it cant be divulged. The destination is the publickey that is generated each session (or transaction), so if there is no account, then it cant be correlated to the IP address. Even when there are a small number of nodes, there is privacy with this method and I believe that is quite unique.

This does raise the issue of spoofing, so there will need to be authentication of some public account before any transactions are done, but there is now an automatic cloud based public key exchange based on user handles, no crazy long numbers to deal with.

James

https://github.com/jl777 16 hours a day of coding and testing the network.

Plus all the other people who have been assisting him day in and day out.

Cliff notes: A ton of code and work has been done already.

why not creat qq group？