Topic: BTCD is no more - page 199. (Read 1328507 times)

need some help, wallet sync problem.   thanks!

Beautiful site buddy

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

site looks great, nice work

Digital ocean as several data centers so we could spread them out.

Amsterdam, San Francisco, New York, London and Singapore

one way to find out
as far as SuperNET is concerned, a BTCD node has ip:port, but it is based on ipv4 so not sure how the ipv6 will map to ipv4 addr...

Technically you can run many. Simply make use of the rpcport= and port= config options and they'll each run on their own instance, port, wallet etc... But will SuperNet know how to connect on custom ports and will it work....

not sure if multiple BTCD can be run on a single machine, but if there are two virtual machines each with separate ports, it is possible

James, I'm looking into some pricing now. Question though. It is feasible to run one instance of NXT and then two BitcoinDark (one on ipv6 and one ipv4). If so could get twice the bang for the buck at one of the places I'm looking at it provides 1 IPV4 and 1 IPV6 IP per vps....

https://bitcointalksearch.org/topic/m.9169365
seems DRK is being stolen via this exploit?
I never felt comfortable with the whole mixing thing where you are literally sending your coins to some random node. This is why Teleport is "direct" peer to peer. As long as the telepods are not compromised, your funds are not compromised.

James

He was able to verify a message and get a proof of identity

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

I have a 1000 BTCD bounty already, but we can certainly be more active about this. I know a lot of people have tried to find something wrong and would love to proclaim some horrible bug in my code.

do you have URL about the darksend exploit?

I wasnt even aware of that, this is the problem with closed source as it takes a lot of people looking at something to find these things. Also, this explains why the price has been down recently. we share "dark" with darkcoin

James

Might want to add this to a shops section in the OP or something...

I wonder if it would be a good way to bring attention to ourselves to publicly request the crypto community to analyze libjl777 for security flaws. If they can't find any, this will reflect good on us. If they can, we can avoid an embarrassing situation like DarkCoin just had when they open sourced DarkSend and an amateur coder found an exploit within hours. What do you think?

Pushed a new version that adds random delay to packets, this makes it harder for an attacker to correlate packets coming in and going out. Since these packets are all exactly 1400 bytes and fully encrypted, there wasnt much for the attacker to analyze, now even that is fuzzy

James

So you just made an account to post on here and say this?


fuck off

FANTASTIC!!

Really cool video.

James

In the last week, I coded the Kademlia DHT, MofN filesystem and multisig API, while I helped others issue a few assets.

What new tech this is silly LTCD actually do? I notice it has not even applied to be part of SuperNET, probably due to lack of any actual tech.

The price has indeed dropped 50% from the SuperNET ICO created peak, the current oscillation point is around .012 so we are one third down from there, which is a significant drop, but when BTC drops to $275 there is a ripple effect.

Anyway, look forward to hear what awesome tech the LTCD has that will make it fundamentally increase in value. BTCD peoples know that the price and value are not always in lockstep, this is how they make more money.

The SuperNET ICO did create some delay, but in any case we dont have the GUI yet, so not sure if it has caused any time to market delay. It did however create a 10x larger audience for generating revenues from.

James

P.S. I have been buying BTCD and certainly not selling at these silly bot made prices.

I offer VPS (www.badass.sx). Perhaps something?

It seems you're trying to create panic selling to buy cheaper coins. LTCD is just a misuse of the BTCD's name and is a shit coin .
Please Get out from this thread.