I am also surprised that 3rd wallet is still uncracked. I've got several PMs with "thanks for the money, man!" stating that they will cracked it in a week or two : )
Looks like they miscalculated something...
Anyways... with rising prices and another 10 months to go (2 years total) there is still plenty of time to crack it. Also my hint reduces the time for a brute force attack quite a lot (about 35%).
Topic: I'm BIP38 curious, please help me out! - page 2. (Read 8608 times)
Can you tell us what was/is the first pass?
First password is "BarT".
Wow !! Dude good for you !! Well done !
Thanks OP for doing this its great !
Lol? He already did that 1 year ago and this challenge isnt done yet. Theres still 1 wallet ( third wallet) which still didnt got cracked. Damn, i hope i know whats password in third wallet since the prize is high.
Can you tell us what was/is the first pass?
First password is "BarT".
Wow !! Dude good for you !! Well done !
Thanks OP for doing this its great !
It took ~20 hours on three n1-highcpu-16 machines on Google Compute. Each one did ~50 passwords per second, 150 total.
It cost around $38 overall.
At this rate it would take up to 4 years to crack the Third password. At $38 for 20 hours it's clearly not worth it.It cost around $38 overall.
Here is a small password hint: If you divide the number of UPPERCASE letters by the number of lowercase letters you get an integer.
So that means:0 UP 6 low: 0/6=0: integer
1 UP 5 low: 1/5: nope
2 UP 4 low: 2/4: nope
3 UP 3 low: 3/3=1: integer
4 UP 2 low: 4/2=2: integer
5 UP 1 low: 5/1=5: integer
Here is a small password hint: If you divide the number of UPPERCASE letters by the number of lowercase letters you get an integer.
This should give you a nice 35% speed boost!
This should give you a nice 35% speed boost!
One year went by and 3rd wallet is still loaded with bitcoin : )
I decided to keep this experiment going for another year. I've also added extra 0.5BTC and updated the OP.
In case this wallet is not cracked in a year, I'll take back 1BTC and publish the password.
Happy cracking!
I decided to keep this experiment going for another year. I've also added extra 0.5BTC and updated the OP.
In case this wallet is not cracked in a year, I'll take back 1BTC and publish the password.
Happy cracking!
Okay, total Newbie question coming.... ready for it?... wait, wait, wait.... before i ask and ridicule myself, let me at least state that I had absolutely Zero knowledge of anything more difficult than very basic html until I started school recently for programming, so with that being said...
Where the hell do you go to even find the wallets so you can crack them?
That's what I don't get about offline wallets.... I get taking the btc offline for storage; I get sweeping/importing it back online.... but where is the hub, the port, the dock, the space station?!?!?!?
See, total Newb question...
Where the hell do you go to even find the wallets so you can crack them?
That's what I don't get about offline wallets.... I get taking the btc offline for storage; I get sweeping/importing it back online.... but where is the hub, the port, the dock, the space station?!?!?!?
See, total Newb question...
I don't get the question of where is the port/hub/dock...? What do you mean?
He created a wallet, I assume via bitaddress.org and encrypted it.
People can't crack a 5 char pass and they thing they'll get into my 25+ char pass.. Funny.
This is a sweet idea non the less.. tempted to add a little more BTC to inspire more people.
This is a sweet idea non the less.. tempted to add a little more BTC to inspire more people.
Okay, total Newbie question coming.... ready for it?... wait, wait, wait.... before i ask and ridicule myself, let me at least state that I had absolutely Zero knowledge of anything more difficult than very basic html until I started school recently for programming, so with that being said...
Where the hell do you go to even find the wallets so you can crack them?
That's what I don't get about offline wallets.... I get taking the btc offline for storage; I get sweeping/importing it back online.... but where is the hub, the port, the dock, the space station?!?!?!?
See, total Newb question...
Where the hell do you go to even find the wallets so you can crack them?
That's what I don't get about offline wallets.... I get taking the btc offline for storage; I get sweeping/importing it back online.... but where is the hub, the port, the dock, the space station?!?!?!?
See, total Newb question...
Is there anyone working on last remaining private key or did you give up?
The wallet still has 0.5BTC, I would surely think there is incentive to crack it.
Is there anyone working on last remaining private key or did you give up?
Can anyone here teach me a bit about this BIP38 cracking?
I want to learn a bit about it
I want to learn a bit about it
Code here -> https://github.com/Dirbaio/bip38-cracker
I've put installation instructions in the readme. Tested with Ubuntu 14.10.
Actually there was this other repo that was linked earlier ( https://github.com/cscott/bip38-cracker ) that is quite faster, probably because it uses scrypt-jane. I fixed it up to read the passwords from stdin so I can either crack from a wordlist or a generated list. Stuff's explained in the README.
It took ~20 hours on three n1-highcpu-16 machines on Google Compute. Each one did ~50 passwords per second, 150 total.
It cost around $38 overall.
So yes, cracking 5-char passwords is definitely feasible for relatively cheap. Would be way cheaper if I had used my own hardware.
The password? The cracker sent me the coins and then I destroyed the instances without writing down the password, silly me. Sorry!
I've put installation instructions in the readme. Tested with Ubuntu 14.10.
Actually there was this other repo that was linked earlier ( https://github.com/cscott/bip38-cracker ) that is quite faster, probably because it uses scrypt-jane. I fixed it up to read the passwords from stdin so I can either crack from a wordlist or a generated list. Stuff's explained in the README.
It took ~20 hours on three n1-highcpu-16 machines on Google Compute. Each one did ~50 passwords per second, 150 total.
It cost around $38 overall.
So yes, cracking 5-char passwords is definitely feasible for relatively cheap. Would be way cheaper if I had used my own hardware.
The password? The cracker sent me the coins and then I destroyed the instances without writing down the password, silly me. Sorry!
Wow, congratulations! Lots of computing power is required! Are you trying the 6 random letter challenge?
I guess if OP not giving further hint, it will not be cracked in many years.
@Dirbaio: Congrats!
I hope there are hackers out there going after the last one... I am really curious how long will it take...
I hope there are hackers out there going after the last one... I am really curious how long will it take...
PS: the tool I linked is also outdated. If you need updated files and help setting up, feel free to send me a PM.
Can you make a github fork like how Dirbaio did? Code here -> https://github.com/Dirbaio/bip38-cracker
I've put installation instructions in the readme. Tested with Ubuntu 14.10.
Actually there was this other repo that was linked earlier ( https://github.com/cscott/bip38-cracker ) that is quite faster, probably because it uses scrypt-jane. I fixed it up to read the passwords from stdin so I can either crack from a wordlist or a generated list. Stuff's explained in the README.
It took ~20 hours on three n1-highcpu-16 machines on Google Compute. Each one did ~50 passwords per second, 150 total.
It cost around $38 overall.
So yes, cracking 5-char passwords is definitely feasible for relatively cheap. Would be way cheaper if I had used my own hardware.
The password? The cracker sent me the coins and then I destroyed the instances without writing down the password, silly me. Sorry!
I've put installation instructions in the readme. Tested with Ubuntu 14.10.
Actually there was this other repo that was linked earlier ( https://github.com/cscott/bip38-cracker ) that is quite faster, probably because it uses scrypt-jane. I fixed it up to read the passwords from stdin so I can either crack from a wordlist or a generated list. Stuff's explained in the README.
It took ~20 hours on three n1-highcpu-16 machines on Google Compute. Each one did ~50 passwords per second, 150 total.
It cost around $38 overall.
So yes, cracking 5-char passwords is definitely feasible for relatively cheap. Would be way cheaper if I had used my own hardware.
The password? The cracker sent me the coins and then I destroyed the instances without writing down the password, silly me. Sorry!
Well... you seem to have a lot horsepower
Quite a bit more than my modest 4 cores.I'm using this https://github.com/cculianu/brute38 as it's easier to setup the wordlist, allows stopping and resuming and it allows to split the work for several computers. I don't know if the tool you linked is capable of the last two.
Meanwhile, I tested your tool. It has about the same performance as the tool I'm currently using on my devices (about 1 password/second/per core). It would be pretty cool to measure both tools face to face, but the differences in hardware are just too big
PS: the tool I linked is also outdated. If you need updated files and help setting up, feel free to send me a PM.
Code here -> https://github.com/Dirbaio/bip38-cracker
I've put installation instructions in the readme. Tested with Ubuntu 14.10.
Actually there was this other repo that was linked earlier ( https://github.com/cscott/bip38-cracker ) that is quite faster, probably because it uses scrypt-jane. I fixed it up to read the passwords from stdin so I can either crack from a wordlist or a generated list. Stuff's explained in the README.
It took ~20 hours on three n1-highcpu-16 machines on Google Compute. Each one did ~50 passwords per second, 150 total.
It cost around $38 overall.
So yes, cracking 5-char passwords is definitely feasible for relatively cheap. Would be way cheaper if I had used my own hardware.
The password? The cracker sent me the coins and then I destroyed the instances without writing down the password, silly me. Sorry!
I've put installation instructions in the readme. Tested with Ubuntu 14.10.
Actually there was this other repo that was linked earlier ( https://github.com/cscott/bip38-cracker ) that is quite faster, probably because it uses scrypt-jane. I fixed it up to read the passwords from stdin so I can either crack from a wordlist or a generated list. Stuff's explained in the README.
It took ~20 hours on three n1-highcpu-16 machines on Google Compute. Each one did ~50 passwords per second, 150 total.
It cost around $38 overall.
So yes, cracking 5-char passwords is definitely feasible for relatively cheap. Would be way cheaper if I had used my own hardware.
The password? The cracker sent me the coins and then I destroyed the instances without writing down the password, silly me. Sorry!
I would like to get in on this too.
I just have no idea on how to do the cracking.
But it would be cool to learn ;P
I just have no idea on how to do the cracking.
But it would be cool to learn ;P
And I added the Fourth one with 5 random characters using only lower case letters from "a" to "z".
That sounds more affordable than the 6-char one 
Will give it a try now.
What tool did you use? Any good tutorials around?
I used this one: https://github.com/notespace/bip38-cracker
It's quite broken though, I had to fix it. I'll try to clean it up and post it to my github soon. Here's a quick summary of what has to be fixed:
- picocoin submodule broken -> point it to https://github.com/jgarzik/picocoin
- Fix build scripts
- (This one drove me nuts) EC point conversion is broken, it should convert the passpoint as compressed and the pubkey as uncompressed, it was doing both compressed. I made a quick ugly hack in picocoin to workaround this.
Seems like you have quite a bit of processing power. Congratulations, what was the pass on this one?
And I added the Fourth one with 5 random characters using only lower case letters from "a" to "z".
That sounds more affordable than the 6-char one Will give it a try now.
What tool did you use? Any good tutorials around?
I used this one: https://github.com/notespace/bip38-cracker
It's quite broken though, I had to fix it. I'll try to clean it up and post it to my github soon. Here's a quick summary of what has to be fixed:
- picocoin submodule broken -> point it to https://github.com/jgarzik/picocoin
- Fix build scripts
- (This one drove me nuts) EC point conversion is broken, it should convert the passpoint as compressed and the pubkey as uncompressed, it was doing both compressed. I made a quick ugly hack in picocoin to workaround this.
Jump to: