Pages:
Author

Topic: Private key (privkey) hunters - unite! - page 3. (Read 15279 times)

legendary
Activity: 1372
Merit: 1123
June 11, 2018, 02:09:22 PM
#32
People win all the time because the chance to win is equal to the number of tickets sold. It's not rare that someone wins, it's rare that you win.

Then I misunderstand the Powerball, because I'm talking about matching the numbers randomly pulled. Your chances of matching random numbers would be unaffected by the random numbers that others have chosen. Their "guesses" do not make your guess any more or less likely to be correct. Again, I might not understand how lotteries work I guess, but this is how I understand it. How are the chances equal to the tickets in a lottery of random numbers? More tickets makes it more likely that someone wins, but it wouldn't make your chances vary.

When comparing Bitcoin to the Powerball lottery, I think it's safe to say you're more likely to win that lottery without buying a ticket, than finding a collision on a private key.

You're over exaggerating, unless we're operating on the assumption that you can win with a stolen ticket, or something? I do see your point though.

Humans are very bad at creating random keystrokes.

Bee Boop.

It's easy to confuse a theoretical chance with a real chance.

Apparently, because I do not know the difference. I've thought on this for hours and I cannot figure out the riddle. Help me understand theoretical chance Vs. real chance, genuinely, I am interested.

Example: You can randomly generate my phone number, call me, and tell me my creditcard number. Although this sounds far fetched, it's still 1461501637330902918203 times more likely than finding a private key collision.

Show your work for this math problem. What are the odds of me randomly generating your phone number, credit card and catching you at a good time for a phone call?  Wink
Since I'm illiterate on vocabulary and semantics, collision = randomly generating a previously randomly generated Private Key, right?

That's why it's very important to generate your private keys at random. If your random isn't random, someone else can reproduce it.

Humans are almost as bad at programming random number generators as they are typing random numbers.
copper member
Activity: 193
Merit: 255
Click "+Merit" top-right corner
June 11, 2018, 09:41:35 AM
#31
We just found a really interesting ETH private key:

Code:
Privkey: 64e604787cbf194841e7b68d7cd28786f6c9a0a3ab9f8b0a0e87cb4387ab0107
Address: 0xf46b6b9c7cb552829c1d3dfd8ffb11aabae782f6

~

Pretty awesome, no?
It would be pretty awesome indeed, if this private key wouldn't have been published 10 months ago already.

How very curious. Because that short blog post doesn't mention WHY they use that private key in their example.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
June 11, 2018, 09:16:45 AM
#30
We just found a really interesting ETH private key:

Code:
Privkey: 64e604787cbf194841e7b68d7cd28786f6c9a0a3ab9f8b0a0e87cb4387ab0107
Address: 0xf46b6b9c7cb552829c1d3dfd8ffb11aabae782f6

~

Pretty awesome, no?
It would be pretty awesome indeed, if this private key wouldn't have been published 10 months ago already.
copper member
Activity: 193
Merit: 255
Click "+Merit" top-right corner
June 11, 2018, 08:43:36 AM
#29
We just found a really interesting ETH private key:

Code:
Privkey: 64e604787cbf194841e7b68d7cd28786f6c9a0a3ab9f8b0a0e87cb4387ab0107
Address: 0xf46b6b9c7cb552829c1d3dfd8ffb11aabae782f6

https://etherscan.io/address/0xf46b6b9c7cb552829c1d3dfd8ffb11aabae782f6

What's cool about this one?

It received 21 ETH from the genesis block! Check the first transaction on the blockchain (link above).

How did we find it? Wordlists, math and blockchain APIs (our own scripts).

Pseudocode:

keccak-256sum("ABC123*") = 64e604787cbf194841e7b68d7cd28786f6c9a0a3ab9f8b0a0e87cb4387ab0107

(* The phrase is actually NOT "ABC123", but you should be able to reproduce this one quite swiftly, with a basic wordlist.)

From there, it's two relatively simple operations, including elliptic curve, to derive the public address.

Pretty awesome, no?
jr. member
Activity: 35
Merit: 2
June 10, 2018, 05:17:07 PM
#28
But the chance of me finding a key: 100%.

The quantum computers is a key. Nobody know how AI works, but AI drives your Tesla Wink
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
June 10, 2018, 01:45:31 PM
#27
~ the chances of winning the Powerball lottery are something like 1 in 300 million and it happens all of the time.
People win all the time because the chance to win is equal to the number of tickets sold. It's not rare that someone wins, it's rare that you win.

Back to Bitcoin: I can generate a random private key right now. The chance of me finding that key: 1 in 1461501637330902918203684832716283019655932542976 !
But the chance of me finding a key: 100%.

When comparing Bitcoin to the Powerball lottery, I think it's safe to say you're more likely to win that lottery without buying a ticket, than finding a collision on a private key.

Quote
I could type random keys on my keyboard
Humans are very bad at creating random keystrokes.

Quote
and potentially end up with an old Satoshi address at my disposal.
No you can't! It's easy to confuse a theoretical chance with a real chance.
Example: You can randomly generate my phone number, call me, and tell me my creditcard number. Although this sounds far fetched, it's still 1461501637330902918203 times more likely than finding a private key collision.

Quote
and increases exponentially when any of these attackers is using a method more effective than simple random generation or brute-force. Sophisticated hacks have a better chance than these figures would suggest.
That's why it's very important to generate your private keys at random. If your random isn't random, someone else can reproduce it.
newbie
Activity: 4
Merit: 0
June 10, 2018, 01:27:17 PM
#26
To be honest never taught about that, what are the odds to hit a wallet with bitcoin in there
legendary
Activity: 1372
Merit: 1123
June 10, 2018, 09:33:02 AM
#25
I'm having an existential crisis right now. Maybe it's because I have a poor understanding of math, but the chances of winning the Powerball lottery are something like 1 in 300 million and it happens all of the time. Statistical improbability does not equal impossibility, in fact it's tangibly the opposite. I could type random keys on my keyboard and potentially end up with an old Satoshi address at my disposal. The chances that someone pops a Private Key increases each time more people are attempting to do so, and increases exponentially when any of these attackers is using a method more effective than simple random generation or brute-force. Sophisticated hacks have a better chance than these figures would suggest.
copper member
Activity: 282
Merit: 31
June 10, 2018, 09:17:10 AM
#24
Did any of you try to access wallets by guessing the seed? I think it might be easier to create a program that randomly checks various seed combinations than trying to find a private key with a positive balance. As time goes by there will be so many seed combinations that a modified password guesser linked to a dictionary might do the job. And this time if you'll able to find something it might not be a single address but a bunch of them. You might even get lucky and get into a wallet owned by a treasure hunter like yourself Wink

Electrum has a dictionary size of 1626 words and uses 12 of them randomly, producing 1626^12 possible combinations, which is close to 10^38 combinations. Good luck finding a collision. It will take quite a while. Example:

If somehow could test 1 billion combinations per second (arbitrary number I just came up with), we need 10^(38-9) = 10^29 seconds to try them all. That is approximately 3.17*10^27 years.

The universe has existed for about 13.8*10^9 years.

You see where this is going... right?

I think that the last few words are a checksum, so your chances are slightly better than that (but still impossibly low).
newbie
Activity: 16
Merit: 0
June 10, 2018, 04:20:23 AM
#23
It's reasonable for you to do so although the odd might not in your favor but yet "nothing is unhackable".
sr. member
Activity: 1330
Merit: 258
June 04, 2018, 12:58:18 AM
#22
I'm interested but I don't understand.. How can use this "empty" private key? any reason please..
I don't check keys yet.. Can claim forks?
member
Activity: 963
Merit: 57
June 03, 2018, 04:30:46 PM
#21
Why are people still doing this, if the probability of finding a private key that is used, is almost zero?
-snip-
Yup, by brute-forcing the key, the chance to hit a collision is close to 0.0000000000000000000000000000001%. Wait,

No, what they talking about (in this thread) are those neglectfully stored wallet.dat files, private key backups, paper wallet images or other forms of backups which potentially have funds.
History can tell that some people are stupid enough to store those (not only wallets but passwords and sensitive info too) directly in the internet without "hiding" the files with a disguised file name, file type, etc.

This one for example:
Found more than 10 wallets with a positive balance without any password protection. Not entirely sure how or why you come up with the idea to put your wallet.dat in your public Dropbox folder. Those were the days...

@OP, this isn't "hacking" and... use this to display the image (the link must be the image's direct link that ends with ".png/.gif/.jpg"):
Code:
[img alt=img height=420]https://i.imgur.com/PrBSxN8.png[/img]
Winning a big lottery also has a small chance, you will never know unless you try. The numbers do not work always like that, technically you have two options you can find one with balance or not. Why there are doing this? Because they can.
full member
Activity: 634
Merit: 106
Europe Belongs To Christians
June 02, 2018, 03:39:18 PM
#20
My fellow crypto hackers. I've been into finding BTC private keys for a little more than a year. I have slightly less than 18k private keys in my own database.

As some sort of proof, here are 50 privkeys - try importing them in for example Electrum

Code:
L3wtCheT3Tvchz6WxsQgVmYopxDKBMxXKC1UpLnVJzEFi34maKLx
KzGk41jwqyoqJN3Rsbv2jDUKQBWYfMLnAke3F89U5oWwf3cauWP3
KxyHuRb7SaTkj36ynts6S58EtFYWDkwcLc3E5WpSdJkcVwgyFgaS
5KkjcrNnP1avWB5g2PimyreVdX5FN8e91UsyerK7z5pGcf6WCYD
5KknpBbehjZ4DRBStfMyd68VNP63rtFHusYaNuDqaE78N948ALf
5KkkZ48EaBs5gmY7W8pAb1cu1KHXVPH4xujT6vmyuYR4WyZ4tmn
5KkmcE7NJTSF9As6we7upSkX9dFxBq9eZNXvfNtyyaKmSbG9hUz
KyEq2YmegzAtz4ADyVowX3fqpvXUinPuTjSknsp218U2zY1Qmi5G
KyfaCbfHkzToiBpawkT1ik3TjQjFfaztgyDyzRHmgGEyz7dTArU4
L4G94NBReR1ZwRkdMSLP41nKXiooLxF9u6YVGp1uPe1eDVeN7qB4
5KkmYchw1wBKCzdY7G7tc5WF6WY5PkCmZxHXi9kYfHfyEWqY1gp
L3uSFVXSUretVNDccCBDPjLSSneCcXaeZPTfe9FS9s3SKAYfdeL6
5Kkjh1TrXpfPQGiEMcptaGBLf8h1KUbtn3n86dmqUoVqPfEfb1P
5KknEJnLyFiGgbUE6ciiGHMQez7o1zW4hMo4VZLpkdSsowuUgPQ
5KkhJ2is3EW8H56n6AvgqT1kWqWh6YhM4KM7ttfjdzrw1qJRyju
KyKQRUE38VFV6iVuX4yJ7GCGrRiquhTSoV3BLmLvCqF6RPXan67Q
5KkkCDvzfsxwTF4NQWsPNdd5ZkcgcGviZWevvQqfYp3ex45VypG
5Kko7c8fGKVSChc8PWJnzEFxXwVTvWJHZVUg8nyGmy3U9DXRMPp
L49HFoB1iFEvzXQn1agpggYGENHTW3khEL4rRArYrcWQcm1iXw4n
L4bSP2b1tBvwnuMrDoZm4vziWhrbzwBtwrsVwmPJqTDUWxCXJH6q
KyAFnDsPNN7DypKeS1wsT6Qzx9A3qGd53uWNeCuvCDjumYEPkoPj
5KkgzEYsJbifwJuqxTPSgkUGstYwX5HKPFucrM776qCwoMdwt59
5KkjenRdxoneEU8Mi8QvRFNuA6jPuiV7Wn9mVobsJiRB2uDXYsN
5Kkg2t2deWnTZrrSRG9jSByMDFKBxQvtYmPd5mycR6DFZHtiQjY
L4XnHhvLC1b4ag9L2PM9kRicQxUoYT1Q36PQ21YtLNkrAdWZNos6
KzK4uyoSm7Bdf3p91P4zVhS4cM4Pq87oCegWf4DcPrqiUDsLfDDt
KyhAKoDY9bfS8ckz2GapefFZfCKMgYTTb1FV2uH3LW2UjvY4xQTM
L3iDb3whFacS3pXFtcJfFLrxpBdJPHL5hUezgMAyYhPzEQhixgKN
5KkgNphSWbFy1r4Eobq1Pbb8kcG1geUpasi597T317HGhP8pYBe
Ky593tmxMTKEs9RjWvZ7bPMNa86wpsxm6di3X48kj4qpPaAj1ygs
5Kkk3dG43gJGHm4SaFC4qRGF7MYG4ShZZ8ESDSiKti1nu71v6Z5
5KkmVdDfTg2QnsMPcyqzbLLX7bZJx4nJATRyLJ9WXy6zDvYwaTR
5KkhGSzfoEaaYdKKeJuq3A7tmPzQdGYxZT2rm71XCAezxn8j6cT
5KkhgqewuqUTXSXZK4oTDi6rg4MHLssE5bh14oZH9NDRrwVdRvJ
KyUYJCbdvkdqWv7csuNHKWsGDcCi5YVXFaP2kfXtDpDNhykCuF6h
5KkmnJwzHL3kTWd8SAkssLmB2yRgUyYoA8X6jn73yfRxHVJYsru
5Kki22dZ3p9mLHvamV9mozC6ypUpq9ZSBa977eaYnec4EdkTLae
5KkhmdqyvaQwuhQ1cfQJCm1xfW4NXV6iDVRuRmVhXMPzGoMEm2s
5KkgASK9mPUrLAogFXZ9cMkxdkP1LNPEoFDVY2FfT64wBQs3fox
Kxk1JRsf6x1aUzN4Gff8ByFX3Jn7XP4NknGZoV6ovaEEVVJF5txf
L4QXUpcMgLC3NxrHgA9EpwAd5pRAkJfh2TvhYATXTW9fgnJuCWRn
Kxntb6r9WjUSJvajfKPWDrJvMVake5J4hBwEd5c4iGepHTbwqi8r
Kxx7AQStazNq2bhBb9nMpfZCKcdvrmKaEtUFskzcmAtVU94Y1jj4
KzedceVxZmamK3KwjpHisZkL7FWUmZnBMZQJTzAWzwbE7zwquaMd
L4rK1yDtCWekvXuE6oXD9jCYfFNV2cWRpVuPLBcCU2z8TrisoyY1
5Kkg7F7nvwy8uKtQsaKZWr9FGPMnM4Vs9nf7LuBXRdxUGZyMAtm
5KkizbG8giTgVgMgS9t1XMHNnxoUEEa2WkB8e1EoArYsqUoGDku
5KkjX2EQbKW1kJk9tRvgvbKcWxjhSicy2DUirQZSzTJ4M9Vd3UD
5KkhNgCMwzjEF7sCWXfKx7v7DHtthU3Jk6jmHHx5AaFnErA3Dzp
5KkmMUpsjKB3gKWzvDA1gsbDFsLFE5Z9H3JRsNSdVSsNFeyJU8D

...and you will get something like (sorry, seems like I don't have the required rank to embed images):

https://imgur.com/a/NwN6ZWA

The vast majority of the privkeys I've discovered are NOT from brainwallets (i.e. weak SHA256 hashes). Image search for QR-codes was nice for a while though, but those days are over. I have a couple of other techniques that I'm fairly sure anyone else hasn't thought of.

Every privkey in my database corresponds to a BTC address with at least two transactions on the blockchain. I throw away all "empty" privkeys.

I have a large Bitcoin Core wallet containing all my discovered privkeys. Five smaller transactions happened within the past week.

Anyways.... I was thinking maybe someone here has the same hobby as I do? Care to hook up and share some thoughts and strategies?

update your electrum !, its outdated
newbie
Activity: 24
Merit: 0
June 02, 2018, 12:32:25 PM
#19
Nice thread, I'm a treasure hunter myself Smiley And yes, like everyone here i know is 100x time more possible i end up fucking scarlett johansson than actually finding anything by bruteforcing.

I have however, found some keys with balance using unconventional methods. Thats the key (no pun) to find private keys. Methods come and go (Bruteforced brainwallets for example). Lots of other methods are dead and so will be a lot more in the future, just a matter of innovating!

Right now i thought, for fun, to develop a script to do old school bruteforcing, shooting in the dark without any specific order, just to see what pops up.

I began by running directory.io clone on a vps, modifying it a bit to display keys so a python script can pick them up and compare it with around 2m known addresses with funds. This beta version is doing around 6000 kps (keys per second) so its quite trashy at the moment, as it does around 500m keys per day

Currently modifying it to:
use 100% cpu, its using barely 30% atm. Multiprocessing, etc.
Convert the golang script to python so it can generate/check on the fly instead of retrieving an html page with the keys
Once this is done, modify the script to become a sort of botnet/pool that can check and upload to a server once it opens in a computer.

The funniest thing is that even that way, i wont find anything Grin!!!


I then guess you are aware of the Large Bitcoin collider. At the time of writing, running at 673.11 Mkeys/s. They've found a few collisions. The odds are not in your favor, diplomatically.

Pure bruteforcing is a dead end.

Think of ways that significantly reduce entropy is my tip. There are a number of ways. People have posted a few, and I have come up with one or two methods myself. Overall however, mining is still much more profitable than going after dust* bruteforce-stylee.

* Yeah, MOST addresses with a positive balance on the blockchain contain dust, hardly worth the effort.

I managed to scale it to 1Mk/s with some tweaks on a few spare vps's I have, they aren't doing anything so is not like im investing on it or anything, it was a fun project to make though. I'm aware of the LBC, i ran it for a few minutes but preferred to make my stuff instead ;P

But of course, its better to find human-fault keys. I have had luck with ETH keys too Smiley
legendary
Activity: 2478
Merit: 1360
Don't let others control your BTC -> self custody
June 01, 2018, 06:45:43 AM
#18
Did any of you try to access wallets by guessing the seed? I think it might be easier to create a program that randomly checks various seed combinations than trying to find a private key with a positive balance. As time goes by there will be so many seed combinations that a modified password guesser linked to a dictionary might do the job. And this time if you'll able to find something it might not be a single address but a bunch of them. You might even get lucky and get into a wallet owned by a treasure hunter like yourself Wink

Electrum has a dictionary size of 1626 words and uses 12 of them randomly, producing 1626^12 possible combinations, which is close to 10^38 combinations. Good luck finding a collision. It will take quite a while. Example:

If somehow could test 1 billion combinations per second (arbitrary number I just came up with), we need 10^(38-9) = 10^29 seconds to try them all. That is approximately 3.17*10^27 years.

The universe has existed for about 13.8*10^9 years.

You see where this is going... right?

Of course, but it's the same when you're trying to bruteforce a private key. The combinations are endless, but that's not what this is all about. Nobody is trying to test all possible combinations, but find a couple that are in use and give access to active wallets. There's a quite high possibility that if you'll start picking 12 random words out of those 1626 and start messing with them in different combinations you will get a single hit. Isn't that what those "treasure hunters" are hoping for?
Why did I ask about the seeds? Because finding a single one can lead to unlocking a wallet with multiple private keys instead of a single one which the collision dudes are trying to find.

No, what they talking about (in this thread) are those neglectfully stored wallet.dat files, private key backups, paper wallet images or other forms of backups which potentially have funds.
History can tell that some people are stupid enough to store those (not only wallets but passwords and sensitive info too) directly in the internet without "hiding" the files with a disguised file name, file type, etc.

Just recently there was a case of a guy being robbed of his coins because he was storing his passwords in a gmail account and had a backup email connected with it. The backup got hacked and through it they managed to gain the password to his main account.
legendary
Activity: 2534
Merit: 6080
Self-proclaimed Genius
June 01, 2018, 02:28:59 AM
#17
Why are people still doing this, if the probability of finding a private key that is used, is almost zero?
-snip-
Yup, by brute-forcing the key, the chance to hit a collision is close to 0.0000000000000000000000000000001%. Wait,

No, what they talking about (in this thread) are those neglectfully stored wallet.dat files, private key backups, paper wallet images or other forms of backups which potentially have funds.
History can tell that some people are stupid enough to store those (not only wallets but passwords and sensitive info too) directly in the internet without "hiding" the files with a disguised file name, file type, etc.

This one for example:
Found more than 10 wallets with a positive balance without any password protection. Not entirely sure how or why you come up with the idea to put your wallet.dat in your public Dropbox folder. Those were the days...

@OP, this isn't "hacking" and... use this to display the image (the link must be the image's direct link that ends with ".png/.gif/.jpg"):
Code:
[img alt=img height=420]https://i.imgur.com/PrBSxN8.png[/img]
legendary
Activity: 3542
Merit: 1965
Leading Crypto Sports Betting & Casino Platform
June 01, 2018, 01:46:20 AM
#16
Why are people still doing this, if the probability of finding a private key that is used, is almost zero? Just look at the numbers involved with this in the following thread : https://bitcointalksearch.org/topic/what-are-the-chances-of-an-address-collision-and-what-happens-when-it-does-104461

There are exactly 2^160 possible addresses and 2^96 private keys and there are only 2^63 grains of sand on all of the beaches of the Earth.

The odds in definitely not in your favour.  Wink
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
I then guess you are aware of the Large Bitcoin collider. At the time of writing, running at 673.11 Mkeys/s. They've found a few collisions.
No, they haven't found a collision, and they never will find one.
To prove a collision,k you need to show two different private keys that create the same address.
member
Activity: 129
Merit: 12
Did any of you try to access wallets by guessing the seed? I think it might be easier to create a program that randomly checks various seed combinations than trying to find a private key with a positive balance. As time goes by there will be so many seed combinations that a modified password guesser linked to a dictionary might do the job. And this time if you'll able to find something it might not be a single address but a bunch of them. You might even get lucky and get into a wallet owned by a treasure hunter like yourself Wink

Electrum has a dictionary size of 1626 words and uses 12 of them randomly, producing 1626^12 possible combinations, which is close to 10^38 combinations. Good luck finding a collision. It will take quite a while. Example:

If somehow could test 1 billion combinations per second (arbitrary number I just came up with), we need 10^(38-9) = 10^29 seconds to try them all. That is approximately 3.17*10^27 years.

The universe has existed for about 13.8*10^9 years.

You see where this is going... right?
legendary
Activity: 2478
Merit: 1360
Don't let others control your BTC -> self custody
Did any of you try to access wallets by guessing the seed? I think it might be easier to create a program that randomly checks various seed combinations than trying to find a private key with a positive balance. As time goes by there will be so many seed combinations that a modified password guesser linked to a dictionary might do the job. And this time if you'll able to find something it might not be a single address but a bunch of them. You might even get lucky and get into a wallet owned by a treasure hunter like yourself Wink
Pages:
Jump to: