This message was too old and has been purged

[starik69]

I will tell you the private key immediately.

Does "immediately" mean more than 24h? 

[1714115706]

1714115706

[1714115706]

1714115706

[urbanogt5]

Also, given his work on the mining thread, I'd say that Evil has lost interest in this little piece of software and has instead concentrated his efforts on cracking the entire curve instead.

Doubt we'll see him again here on this thread, but I stand to be corrected - pleasantly so.

Rit.

You sounds like Evil

[Ritual]

Well, at this point I think we can safely assume this is horseshit.

I hope nobody gave him 2 bitcoins. Damn glad I didn't.

Rit.

[itod]

Well, at this point I think we can safely assume this is horseshit.

-1, it's very interesting.

I hope nobody gave him 2 bitcoins. Damn glad I didn't.

This is debatable, guy needs to pay 10 BTC for the triples somehow. Maybe he got some funds from the academia to finance that.

[Evil-Knievel]

This message was too old and has been purged

[weedoge]

Okay guys, I have found the reason why i am trying to crack those for around 3 days now.

it is clearly not a problem on my side, but the "Secret Exponent" Field is size limited on the brainwallet.org website. Meaning if you paste in a number which is too long, the end gets cut off. DOH!

Please repeat the process with numbers, that actually fit in the secret exponent field completely.
Sorry for this inconvenience ...

If you generate your address completely as to the manual, and the exponent does not get cut off, I will need around 15 minutes per Private Key MAX!

1AHuqqrtfxfmTC4KQNGDX7kedxdgpQnUmD

Pub key: 04db259553306519117692a0175d8abdd8ef2f12fcb3a2a56e7d4879e049f9abdc5a9244906da8f 58879b4de5d0b8c3182e4acfe9c231a379037aba1f5cc541d02

[Evil-Knievel]

This message was too old and has been purged

[Ritual]

Looks like I need to post an apology, so here it is:

My previous response was both premature and immature. Please accept my sincere apology, and congratulations on your successful test.

EDIT: And please give your tool a nicer name 

Thanks,

Ritual.

[Evil-Knievel]

This message was too old and has been purged

[Ritual]

[tsoPANos]

hahah I liked that one 

[weedoge]

Pretty awesome....

but it's a very specific way of generating addresses.

And you have no method of checking which addresses are weak?

Can you attempt to crack multiple addresses at the same time with little performance loss?

[Evil-Knievel]

This message was too old and has been purged

[ny2cafuse]

Disclaimer:
This project is for research purpose only, or to recover lost private keys. It may not be used for any illegal activities and I cannot be held responsible for anything you do with it.

You say it's for research only, but at the end of your video you say the bitcoins in the address are "stolen".  You little comic shows your true intention of just stealing people's coins.  If you were going to do this, why would you announce it?  Wouldn't you just quietly steal all the bitcoins you could find?  It makes no sense. 

And then to top it off, if it really is for research, why wouldn't you just donate the knowledge to the development team to help fix the security hole that you're claiming exists?  You have the possibility of earning more money in donations from the community by providing a fix for what you're trying to prove is a security flaw.  Hell, I'd donate bitcoin to you if you were doing this for the good of the community.  But 2BTC for a copy... it makes no sense.  If it did what you say it does, and it could have very well be proven in the profanity-laced and almost tourettes-like video, why wouldn't you be charging more for it.  2BTC is chump change if this is legit.

Something doesn't add up.  Just my $0.02.

-Fuse

[prezbo]

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

Theoretically yes,
I am offering it for "scientific purpose" only. The buyer must agree not to use it for any illegal activity whatsoever.

For clarification: Collisions mean that there is a private key found, of which the public key matches in 32bits (out of 256) the public key you provided as an input. This (at the current speed) happens several times a minute.

If wanted, I can prove that weak private keys are found within a manner of seconds. Weak private keys are all those, who are significantly close (like several million units apart on the x axis) to one of the 768 rendezvous points on the elliptic curve.

Just want to clarify, this is cracking public keys not addresses. There is currently no known way of getting the public key from the address unless sha256 and ripemd-160 are broken.

However, a very interesting project, Evil-Knievel - but I wouldn't put my money on it actually cracking any public key with actual bitcoins on it (unless it's set up, of course).

[Evil-Knievel]

This message was too old and has been purged

[Remember remember the 5th of November]

So what exactly is a rendezvous point? I can't find anything on Google about rendezvous points about ECDSA or curves

[Yogafan00000]

All horseshit aside, to clarify all of this:

It seems that any reused Bitcoin address is potentially vulnerable to attack because right now there is no way to know if it's close to a rendezvous point?

But addresses that haven't been reused are safe, but only because the public key for that address has not been broadcast yet?  As soon as the public key is broadcast by spending from an address it becomes vulnerable?

I've been noticing rumblings of this before from a privacy point of view, but it seems now we have even more reason to stop reusing addresses.

[Evil-Knievel]

This message was too old and has been purged

[prezbo]

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

Theoretically yes,
I am offering it for "scientific purpose" only. The buyer must agree not to use it for any illegal activity whatsoever.

For clarification: Collisions mean that there is a private key found, of which the public key matches in 32bits (out of 256) the public key you provided as an input. This (at the current speed) happens several times a minute.

If wanted, I can prove that weak private keys are found within a manner of seconds. Weak private keys are all those, who are significantly close (like several million units apart on the x axis) to one of the 768 rendezvous points on the elliptic curve.

Just want to clarify, this is cracking public keys not addresses. There is currently no known way of getting the public key from the address unless sha256 and ripemd-160 are broken.

However, a very interesting project, Evil-Knievel - but I wouldn't put my money on it actually cracking any public key with actual bitcoins on it (unless it's set up, of course).

I have to correct you here. All public keys are publicly available on blockchain.info.

They are once you sign an input, but any half capable wallet won't reuse addresses, making it so once the public key is known the funds will be gone.

edit: I see you already addressed this.