Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SuperNET asset 12071612744977229797, trading symbol UNITY
by
jl777
on 19/10/2014, 07:00:46 UTC

for those who might be interested...

Supernet API thread on supernet forum
https://forum.thesupernet.org/index.php?topic=154.75


user Cassius is documenting API progress here https://forum.thesupernet.org/index.php?board=41.0
appears to be a fresh board

Fresh board, just got started.
I've been sidetracked by writing up James' thoughts on anon communication. I'd really love for people to pitch in and leave their thoughts on the API in those threads. It would make my job a lot faster/easier, and there is a 1000 BTCD bounty if you can break the API. Just play with it, jot down any notes, and see what damage you can do Smiley
The bounty is for a method to deanonymize the telepods.

just did the first telepathic transfer!

try AESpassword.(113d4aea6f1e699670deaa0a647850305466d4d8760b5c34cad4ccc3aef6cc30)
couldnt parse decrypted.(deadbeef)
(s2.4) pass.(113d4aea6f1e699670deaa0a647850305466d4d8760b5c34cad4ccc3aef6cc30) | process_telepathic: key.(1415731214146562750) got.(7fc0f15c70b0) len.25 from 11843209251668136103 dist 38 vs mydist srv 28 priv 36 | 209.126.70.159

That is what was received by the .170 server

>>>>>>>> directsend.[[{"requestType":"findnode","NXT":"17982454456787380714","time":1413700907,"key":"1415731214146562750","data":25},{"token":"c4vm81rl4m295gbb34o4fgbtrfsihonndahasqg54jltspsnm5peo2maetp81381lh002jcn58e9d22 ufa6g6i8em7eqs71cdhscqhfremmgfn0r186dmg3oc3ko1nhpm6v7tqmj9vnejghdirghbada1t4g6m 9r"}]]

the above was send from the .159 server whose pubid is 13434315136155299987 and the private addr is 482478496576188177

The deaddrop address was obtained via need to get s0 deaddrop from 3078458623062153086, which was independently calculated by both nodes and the 170 server published  1415731214146562750

Ran into a bit of a snag as each relay retokenized each packet, so I had to make a passthrough, this actually makes things a bit more confusing as now the same IP will have quite a few different acct #'s

So neither node communicated to anyother node it's IP address, but the message still got through. Instead of broadcasting to achieve this (like bitmessage does), the DHT mechanism is used, and it is log2(N)*K, which is much less than N for any reasonable N and K values.

Now I can add some higher level logic to the IP-less routing, very good progress!

James