Pages:
Author

Topic: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED== - page 45. (Read 54326 times)

legendary
Activity: 1974
Merit: 1077
^ Will code for Bitcoins
If you read the opening post you'll find there is no puzzle, this is a "challenge" that creator put to prove it can not be solved. Whoever he is, motivation probably was to make sure everyone's coins are safe since nobody can solve this challenge as the complexity of the private keys increases, and everyone's Bitcoins are safe. This challenge is also a excellent measure of the power of brute-forcing the known public keys, because if the challenge is impossible for these lower range private keys it is certainly impossible for Bitcoins with normal full key range.
So this challenge is basically a flex on the security of bitcoin towards everyone? I gotta agree that it is a ballsy kind of flex, letting some bitcoin hang so sharks are baited into thinking that they can solve this challenge which is not really the point of the game, it was all to boast the security of bitcoin. But I think that this challenge is not unsolvable, it only takes one person to have a Eureka moment so they can finally crack the challenge and it might not be now but there will come a time that someone will do the seemingly impossible.

If this challenge is solved then the Bitcoin price will quickly go to 0 since it will be broken, anyone would be able to take anyone's coins. So whoever is trying to solve this challenge will in both cases get no monetary value at the end: If he does not solve it he will get nothing, and if he solves the challenge he will again get nothing because Bitcoin will be worth nothing. In any case this challenge is fantastic way to prove nobody can solve it because if someone solves it we will know immediately by BTC price going to 0 US$ on that day on the exchanges, no need to announce the solution. OFC, this will never happen.
sr. member
Activity: 1274
Merit: 293
If you read the opening post you'll find there is no puzzle, this is a "challenge" that creator put to prove it can not be solved. Whoever he is, motivation probably was to make sure everyone's coins are safe since nobody can solve this challenge as the complexity of the private keys increases, and everyone's Bitcoins are safe. This challenge is also a excellent measure of the power of brute-forcing the known public keys, because if the challenge is impossible for these lower range private keys it is certainly impossible for Bitcoins with normal full key range.
So this challenge is basically a flex on the security of bitcoin towards everyone? I gotta agree that it is a ballsy kind of flex, letting some bitcoin hang so sharks are baited into thinking that they can solve this challenge which is not really the point of the game, it was all to boast the security of bitcoin. But I think that this challenge is not unsolvable, it only takes one person to have a Eureka moment so they can finally crack the challenge and it might not be now but there will come a time that someone will do the seemingly impossible.
member
Activity: 406
Merit: 47

If you read the opening post you'll find there is no puzzle, this is a "challenge" that creator put to prove it can not be solved. Whoever he is, motivation probably was to make sure everyone's coins are safe since nobody can solve this challenge as the complexity of the private keys increases, and everyone's Bitcoins are safe. This challenge is also a excellent measure of the power of brute-forcing the known public keys, because if the challenge is impossible for these lower range private keys it is certainly impossible for Bitcoins with normal full key range.

Thank you itod

now I know more about this challenge , I am not join at begin challenge
I read a  little on open post but not to now what happen and overall activity from 6 year ago.

I think normal brute-forcing can not attack bitcoin 256 key success. it is very very hard.

if not have some guide (rank, pubkey) this challenge is not easy to crack and if not use low bits it will be can not solve it

bitcoin very strong on 256bits
now money can not destroy bitcoin price will be move up

have only can destroy bitcoin is algorithm can solve bitcoin but some part not at all.
and technology going fast next it quantum and AI. don't be careless


legendary
Activity: 1974
Merit: 1077
^ Will code for Bitcoins

Can I ask, Who creator this puzzle? puzzle owner group or who donate bitcoin to use for puzzle

Sorry, I am new, Begin late from first time  puzzle 6 year ago.
just want to know. no big deal.

Done have other puzzle unsolved.


If you read the opening post you'll find there is no puzzle, this is a "challenge" that creator put to prove it can not be solved. Whoever he is, motivation probably was to make sure everyone's coins are safe since nobody can solve this challenge as the complexity of the private keys increases, and everyone's Bitcoins are safe. This challenge is also a excellent measure of the power of brute-forcing the known public keys, because if the challenge is impossible for these lower range private keys it is certainly impossible for Bitcoins with normal full key range.
member
Activity: 406
Merit: 47

Can I ask, Who creator this puzzle? puzzle owner group or who donate bitcoin to use for puzzle

Sorry, I am new, Begin late from first time  puzzle 6 year ago.
just want to know. no big deal.

Done have other puzzle unsolved.
member
Activity: 406
Merit: 47

Bitcrack will do it for you; just use --share flag. If you want to break it up into 100 ranges, use --share 1/100; or yes, let python do it for you.

Thank you.
I still learning to use this tools for puzzle other address not have pubkey kangaroo  method
full member
Activity: 1162
Merit: 237
Shooters Shoot...



Hi, MeBender
this is good idea for generate command for BitCrack
How can I generate command like you script done
I try to using easy by excel and display with DEC2HEX function

but I would like to random to run each keyspace one , Have a any idea to do this?

Bitcrack will do it for you; just use --share flag. If you want to break it up into 100 ranges, use --share 1/100; or yes, let python do it for you.
full member
Activity: 1162
Merit: 237
Shooters Shoot...
Hello my friend, your program is not working correctly, you could not go over 35%. I went over with a speed of 1600 Mkey, and in 8 hours about 46,000,000,000,000 passwords, our final range of 18446744073709551615 turns out, 5 more numbers in front, this is a lot.

Maybe my maths is wrong, I certainly mess things up with the hex-dec conversions... Maybe it's more like 17%?

My BitCrack console window currently says:

Code:
Ellesmere        768 / 8192MB | 1 target 150.12 MKey/s (1,655,689,975,443,750,912 total) [15:17:01:05]

So if I am reading this correctly, that's 1.65 x 10^18 keys checked.

And the keyspace is approx 9.22 x 10^18 in size?  I used a hex calculator to subtract the ff[..] from 80[..] and came up with that number in decimal equivalent.  Maybe that's where I went wrong
My friend, you aren't even close...the pool that has been running for over a year, with Billions of Keys per second with hundreds of V100s has only searched about 11 percent of the entire range.
member
Activity: 406
Merit: 47
member
Activity: 406
Merit: 47
member
Activity: 158
Merit: 39
17,95%

to go 7567682061411024895 Smiley

PS. OFC You are not using stride?
newbie
Activity: 4
Merit: 6
What if it was 800000000000000? then now you are only on this site 96FA3142AC800000 is really more like 17%.
newbie
Activity: 3
Merit: 0
Hello my friend, your program is not working correctly, you could not go over 35%. I went over with a speed of 1600 Mkey, and in 8 hours about 46,000,000,000,000 passwords, our final range of 18446744073709551615 turns out, 5 more numbers in front, this is a lot.

Maybe my maths is wrong, I certainly mess things up with the hex-dec conversions... Maybe it's more like 17%?

My BitCrack console window currently says:

Code:
Ellesmere        768 / 8192MB | 1 target 150.12 MKey/s (1,655,689,975,443,750,912 total) [15:17:01:05]

So if I am reading this correctly, that's 1.65 x 10^18 keys checked.

And the keyspace is approx 9.22 x 10^18 in size?  I used a hex calculator to subtract the ff[..] from 80[..] and came up with that number in decimal equivalent.  Maybe that's where I went wrong
newbie
Activity: 4
Merit: 6
Hello my friend, your program is not working correctly, you could not go over 35%. I went over with a speed of 1600 Mkey, and in 8 hours about 46,000,000,000,000 passwords, our final range of 18446744073709551615 turns out, 5 more numbers in front, this is a lot.
newbie
Activity: 3
Merit: 0
So I'm starting to ponder, how on earth has this #64 puzzle not been solved yet?

I have personally solo checked about 35% of the keyspace in the past 15.5 days, with a comparatively slow speed of ~150 MKey/s.

I've seen this #64 puzzle has been the main target for about a year?  And there are several pools checking BKey/s , many other BitCrackers who are getting >700 MKey/s, etc.

I'm starting to get skeptical that the 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN  address is even in the 8000000000000000...ffffffffffffffff keyspace at all.
member
Activity: 406
Merit: 47
Hi,no I'll explain more clearly,I know it's not hard I had the website saved but can't find it again and have tried literally for hours,getting old I guess.I'll use simple ones as an example.

So Address 17 has a pkv decimal value of 95823 which is 000000000000000000000000000000000000000000000000000000000001764f hex value

Address 19 has a pkv decimal value of  357535 which is 000000000000000000000000000000000000000000000000000000000005749f hex value

So I want to find Address 18 and lets say I want to start my scan at pkv decimal value of 200000

How can I turn 200000 pkv decimal value into HuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuh? hex value

I know it's not too hard to find this formula or website  or chart but I'm stumped on it.

I'm working on Address 64 and want to start midway between 63 and 65 which are solved and the hex values are known but can't convert my pkv decimal value "guess starting point" into a hex value.



What you want to do for?
try python have function  string zfill() function try to use it
str.zfill(width)

>>> str = '5749f'
>>> str.zfill(65)
'0000000000000000000000000000000000000000000000000000000000005749f'
>>>


member
Activity: 406
Merit: 47
Yes thanks I forgot about adding the 0's,getting old LOL.

ok, I understand you mean  like (95823) hex number 0x1764f  how to add long leading zeros number prefix right
000000000000000000000000000000000000000000000000000000000001764f

waiting some one know to help answer or keep search on google I thin somebody will done this solution already

member
Activity: 93
Merit: 26
Yes thanks I forgot about adding the 0's,getting old LOL.
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
So Address 17 has a pkv decimal value of 95823 which is 000000000000000000000000000000000000000000000000000000000001764f hex value

Both previous answers do this nicely. You only have to put the missing zeroes in front of the result. If you cannot do that, keep searching.
member
Activity: 93
Merit: 26
Hi,no I'll explain more clearly,I know it's not hard I had the website saved but can't find it again and have tried literally for hours,getting old I guess.I'll use simple ones as an example.

So Address 17 has a pkv decimal value of 95823 which is 000000000000000000000000000000000000000000000000000000000001764f hex value

Address 19 has a pkv decimal value of  357535 which is 000000000000000000000000000000000000000000000000000000000005749f hex value

So I want to find Address 18 and lets say I want to start my scan at pkv decimal value of 200000

How can I turn 200000 pkv decimal value into HuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuhHuh? hex value

I know it's not too hard to find this formula or website  or chart but I'm stumped on it.

I'm working on Address 64 and want to start midway between 63 and 65 which are solved and the hex values are known but can't convert my pkv decimal value "guess starting point" into a hex value.

Pages:
Jump to: