This is actually for cracking public addresses and finding the private key? lol

Don't anyone buy this, it is impossible to brute force a private key, it would take many many lifetimes. This is the protection that addresses give.

Stop playing this, let me use your words and twist them you know what I mean. Just generating a key pair is not brute forcing.

Wait so you can't brute force my address in seconds then? $16 in that address it could be yours. The public key is visible since I have done transactions so if that is what you need it is there.

Then he is talking about hacking brain wallets due to the random entropy being a word or something easy.

No one has broken the ESCDA public key, if he did he would have taken a lot of money and he hasn't. He didn't take my address and the public key is published since I have done transactions with it. He is probably harboring back to the android flaw or something like that. Nothing to be worried about it.

This is just some FUD nothing serious.

This message was too old and has been purged

What you are describing sounds like it efficiently detects partial collisions with your rendezvous points and then from there you may be close enough to crack it in matter of days.    You have not reduced the overall search space for cracking any random address but you have greatly increased your chances and efficiency of cracking an address mathematically close to one of your Rendezvous points.

So by definition, a so called "weak" address is one that is close to a Rendezvous point


If the entire address space is 2^N,
Let A = Log2(#Rendezvous points)
Let B = Log2(#of Addresses you can brute force in few days around any one Rendezvous point)

Then within this few day time limit, you can crack any address that falls in the "weak" space of size 2^(A+B) and cannot crack any address that falls in the "hard" space of size 2^(N-A-B)

Is that about right?  If not can you describe sizes of the weak space that you can attack.

Show nothing but ok keep thinking you have a program that can crack private keys.

Very interesting.

As far as the debate going on here, why doesn't Gweedo just generate a weak address (not just any address, one that meets to criteria that Evil-Knievel sets out) and post it here.  Evil-Knievel can send a small amount of coins to the address, then crack the address and take his coins back?

Alternatively, and considerably more interestingly in my opinion, you could agree on a third party/escrow to generate a weak address.  Then both Gweedo and Evil-Knievel deposit a set (small) amount of BTC to the address.  Then Evil-Knievel has a set amount of time to break the private key before the Escrow sends all of the coins to Gweedo.

Just sayin'