Bitcoin puzzle transaction ~32 BTC prize to who solves it

[james5000]

with 1Mk/s i have a key off 66 puzzle in max 10 days
with 300Mk/s i have a key in 10 hours
if albertobsd want work with me, we can make a call and divide 50/50 the 66, 67 and 68, maybe more

I think that your calculations are some wrong, what formula do you use?
According to my research with 1 Million keys/s the puzzle 66 can take up to 1 million 169 thousand years.

This is the secret, all the techniques that have been tried will not solve 66 onwards, but we can work with my strategy, with a good enough rate even the first blocks wallets can be broken in months.

[Kamoheapohea]

with 1Mk/s i have a key off 66 puzzle in max 10 days
with 300Mk/s i have a key in 10 hours
if albertobsd want work with me, we can make a call and divide 50/50 the 66, 67 and 68, maybe more

I think that your calculations are some wrong, what formula do you use?
According to my research with 1 Million keys/s the puzzle 66 can take up to 1 million 169 thousand years.

This is the secret, all the techniques that have been tried will not solve 66 onwards, but we can work with my strategy, with a good enough rate even the first blocks wallets can be broken in months.

I assume you try to filter out all privatekeys that do not seem random enough. Like repeating patterns in any base (...1111..., ...2222..., ...1234..., 0x...aaaa...). This will reduce the searchspace. But I think the benefit will also decrease exponentially, so you will have to search like 64.5 bit instead of 65 bit for 66 bit puzzle.

[bestie1549]

with 1Mk/s i have a key off 66 puzzle in max 10 days
with 300Mk/s i have a key in 10 hours
if albertobsd want work with me, we can make a call and divide 50/50 the 66, 67 and 68, maybe more

I think that your calculations are some wrong, what formula do you use?
According to my research with 1 Million keys/s the puzzle 66 can take up to 1 million 169 thousand years.

This is the secret, all the techniques that have been tried will not solve 66 onwards, but we can work with my strategy, with a good enough rate even the first blocks wallets can be broken in months.

I assume you try to filter out all privatekeys that do not seem random enough. Like repeating patterns in any base (...1111..., ...2222..., ...1234..., 0x...aaaa...). This will reduce the searchspace. But I think the benefit will also decrease exponentially, so you will have to search like 64.5 bit instead of 65 bit for 66 bit puzzle.

Before BitCrack was developed, everything else happening now could feel more like what James is trying to say right now until might all sound like bullshit if someone that was only scanning keys at the range of a couple hundred thousand keys per second if Brichard had brought that idea to the table to him before developing the code. and right now even WanderingPhilosopher and Albertobsd were abled to develop something even slightly faster than that almost 1.5 times the idea that could has sounded stupid back in the days. We all understand that ideas might look very shabby sometimes when you hear them when they actually haven't been put to test and sometimes those ideas might actually be shabby and rough. It just needs some amount of hard work and the sky is the limit. We have Kangaroo also solving these formulas like it's nothing but before these codes were developed, so much hard work and thoughtful ideas came together to achieve them. If it's worth a thought and logical then it's worth giving a try. Let us just give this a try as suggested and it could actually be the solution that everyone else has been looking for. We have the endormophism in keyhunt "In few words for elliptic curves, an endomorphism is a function that maps points on the curve to other points on the same curve.

One kind of Endomorphism is the Point negation by example the privatekey from puzzle 64"
that was an idea that actually got the code to go even faster than the norm without activation of endormophism.
James could have something logical up his sleeves and we all don't know where this could be leading but let's just hope there's a reasonable amount of solutions this would solve much more easily.

[james5000]

Before BitCrack was developed, everything else happening now could feel more like what James is trying to say right now until might all sound like bullshit if someone that was only scanning keys at the range of a couple hundred thousand keys per second if Brichard had brought that idea to the table to him before developing the code. and right now even WanderingPhilosopher and Albertobsd were abled to develop something even slightly faster than that almost 1.5 times the idea that could has sounded stupid back in the days. We all understand that ideas might look very shabby sometimes when you hear them when they actually haven't been put to test and sometimes those ideas might actually be shabby and rough. It just needs some amount of hard work and the sky is the limit. We have Kangaroo also solving these formulas like it's nothing but before these codes were developed, so much hard work and thoughtful ideas came together to achieve them. If it's worth a thought and logical then it's worth giving a try. Let us just give this a try as suggested and it could actually be the solution that everyone else has been looking for. We have the endormophism in keyhunt "In few words for elliptic curves, an endomorphism is a function that maps points on the curve to other points on the same curve.

One kind of Endomorphism is the Point negation by example the privatekey from puzzle 64"
that was an idea that actually got the code to go even faster than the norm without activation of endormophism.
James could have something logical up his sleeves and we all don't know where this could be leading but let's just hope there's a reasonable amount of solutions this would solve much more easily.

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s 

[zodmode]

Before BitCrack was developed, everything else happening now could feel more like what James is trying to say right now until might all sound like bullshit if someone that was only scanning keys at the range of a couple hundred thousand keys per second if Brichard had brought that idea to the table to him before developing the code. and right now even WanderingPhilosopher and Albertobsd were abled to develop something even slightly faster than that almost 1.5 times the idea that could has sounded stupid back in the days. We all understand that ideas might look very shabby sometimes when you hear them when they actually haven't been put to test and sometimes those ideas might actually be shabby and rough. It just needs some amount of hard work and the sky is the limit. We have Kangaroo also solving these formulas like it's nothing but before these codes were developed, so much hard work and thoughtful ideas came together to achieve them. If it's worth a thought and logical then it's worth giving a try. Let us just give this a try as suggested and it could actually be the solution that everyone else has been looking for. We have the endormophism in keyhunt "In few words for elliptic curves, an endomorphism is a function that maps points on the curve to other points on the same curve.

One kind of Endomorphism is the Point negation by example the privatekey from puzzle 64"
that was an idea that actually got the code to go even faster than the norm without activation of endormophism.
James could have something logical up his sleeves and we all don't know where this could be leading but let's just hope there's a reasonable amount of solutions this would solve much more easily.

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s 

What is your code running on ? and is it on github?

[james5000]

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s 

What is your code running on ? and is it on github?

is running in cuda c++ with a gtx 1650 4GB

Unfortunately I can't share the code yet, because as I said a few days ago, people with more resources or experience will find the keys and my work for months will have been in vain, I dedicated everything to this project and I am absolutely sure that This is the way.

[bestie1549]

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s 

What is your code running on ? and is it on github?

is running in cuda c++ with a gtx 1650 4GB

Unfortunately I can't share the code yet, because as I said a few days ago, people with more resources or experience will find the keys and my work for months will have been in vain, I dedicated everything to this project and I am absolutely sure that This is the way.

Okay that's nice.
Take all the time you need, get 66,67,68 and 69 then share the code when you have gotten enough resources. The sky is the limit. as of right now, if everyone else were thinking the same way you're thinking, Pollard Kangaroo would still be hidden until now, he'd be hoping to solve all the puzzle before releasing the code. what do you think the puzzles are about? 1+1?
The 1+1 stages are all over right now. the bruteforcing part we currently are trying to solve is 66 bits. i know you have a magical code though but if it takes you 1 year on your code it takes everyone else nothing more than 100 years, in regard to the resources or more years for some other people without the resources needed, if you waste too much money to get the resources and it turned out   to be unprofitable. what point does it make then? because after you calculate the expenses to run all that machine then you would understand what it's called. left alone, 67 bits is double 66 bits so imagine you will take 2 years to solve that one.
If the resources stops becoming profitable then what point does it make trying to bruteforce a key that won't yield any profit after expenses and time spent has been calculated. we can all let you know that puzzles are for fun and not for funds. when you finally realize that, you will think twice after wasting about 5 years using your code without finding any keys whereas if you had made it public, someone might develop it and make it better for your hardwork.

[bestie1549]

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s 

What is your code running on ? and is it on github?

is running in cuda c++ with a gtx 1650 4GB

Unfortunately I can't share the code yet, because as I said a few days ago, people with more resources or experience will find the keys and my work for months will have been in vain, I dedicated everything to this project and I am absolutely sure that This is the way.

Okay that's nice.
Take all the time you need, get 66,67,68 and 69 then share the code when you have gotten enough resources. The sky is the limit. as of right now, if everyone else were thinking the same way you're thinking, Pollard Kangaroo would still be hidden until now, he'd be hoping to solve all the puzzle before releasing the code. what do you think the puzzles are about? 1+1?
The 1+1 stages are all over right now. the bruteforcing part we currently are trying to solve is 66 bits. i know you have a magical code though but if it takes you 1 year on your code it takes everyone else nothing more than 100 years, in regard to the resources or more years for some other people without the resources needed, if you waste too much money to get the resources and it turned out   to be unprofitable. what point does it make then? because after you calculate the expenses to run all that machine then you would understand what it's called. left alone, 67 bits is double 66 bits so imagine you will take 2 years to solve that one.
If the resources stops becoming profitable then what point does it make trying to bruteforce a key that won't yield any profit after expenses and time spent has been calculated. we can all let you know that puzzles are for fun and not for funds. when you finally realize that, you will think twice after wasting about 5 years using your code without finding any keys whereas if you had made it public, someone might develop it and make it better for your hardwork.

PLEASE IF YOU FIND A WAY TO COMPLETE THE 66 BITS PUZZLE TAKE THE PRIVATE KEY YOUVE EARNED IT BUT PLEASE TAKE THIS TO HEART THAT WHAT A WISEMAN ABOVE HINTED AT WILL SAVE YOU HUNDRED FOURTY OF THE TIME OF WHAT YOU ARE TRYING TO ACCOMPLISH IN THE END PLEASE JUST HELP US MAKE THE CODE PUBLIC INSTEAD OF JUST WAISTING YOUR LIFETIME BY HUNTING FOR WORTHLESS PRICES AND THROPHIES LIKE THIS I'M SORRY TO TELL YOU THAT YOUVE COME THIS FAR BUT YOU'LL NEVER FINISH PUZZLE 66 IF YOU DON'T MAKE THE CODE PUBLIC FOR DEVELOPING I EXPECT YOU TO SAY BULLSHIT WELL DENIAL IS THE MOST PREDICTABLE OF ALL HUMAN RESPONSES

[james5000]

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s 

What is your code running on ? and is it on github?

is running in cuda c++ with a gtx 1650 4GB

Unfortunately I can't share the code yet, because as I said a few days ago, people with more resources or experience will find the keys and my work for months will have been in vain, I dedicated everything to this project and I am absolutely sure that This is the way.

Okay that's nice.
Take all the time you need, get 66,67,68 and 69 then share the code when you have gotten enough resources. The sky is the limit. as of right now, if everyone else were thinking the same way you're thinking, Pollard Kangaroo would still be hidden until now, he'd be hoping to solve all the puzzle before releasing the code. what do you think the puzzles are about? 1+1?
The 1+1 stages are all over right now. the bruteforcing part we currently are trying to solve is 66 bits. i know you have a magical code though but if it takes you 1 year on your code it takes everyone else nothing more than 100 years, in regard to the resources or more years for some other people without the resources needed, if you waste too much money to get the resources and it turned out   to be unprofitable. what point does it make then? because after you calculate the expenses to run all that machine then you would understand what it's called. left alone, 67 bits is double 66 bits so imagine you will take 2 years to solve that one.
If the resources stops becoming profitable then what point does it make trying to bruteforce a key that won't yield any profit after expenses and time spent has been calculated. we can all let you know that puzzles are for fun and not for funds. when you finally realize that, you will think twice after wasting about 5 years using your code without finding any keys whereas if you had made it public, someone might develop it and make it better for your hardwork.

You're right, I'm just sad to think that all the work wouldn't be paid, I really bet a lot on it, but I'll share the logic and count on everyone's humility.

[Denis_Hitov]

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s  

What is your code running on ? and is it on github?

is running in cuda c++ with a gtx 1650 4GB

Unfortunately I can't share the code yet, because as I said a few days ago, people with more resources or experience will find the keys and my work for months will have been in vain, I dedicated everything to this project and I am absolutely sure that This is the way.

Okay that's nice.
Take all the time you need, get 66,67,68 and 69 then share the code when you have gotten enough resources. The sky is the limit. as of right now, if everyone else were thinking the same way you're thinking, Pollard Kangaroo would still be hidden until now, he'd be hoping to solve all the puzzle before releasing the code. what do you think the puzzles are about? 1+1?
The 1+1 stages are all over right now. the bruteforcing part we currently are trying to solve is 66 bits. i know you have a magical code though but if it takes you 1 year on your code it takes everyone else nothing more than 100 years, in regard to the resources or more years for some other people without the resources needed, if you waste too much money to get the resources and it turned out   to be unprofitable. what point does it make then? because after you calculate the expenses to run all that machine then you would understand what it's called. left alone, 67 bits is double 66 bits so imagine you will take 2 years to solve that one.
If the resources stops becoming profitable then what point does it make trying to bruteforce a key that won't yield any profit after expenses and time spent has been calculated. we can all let you know that puzzles are for fun and not for funds. when you finally realize that, you will think twice after wasting about 5 years using your code without finding any keys whereas if you had made it public, someone might develop it and make it better for your hardwork.

You're right, I'm just sad to think that all the work wouldn't be paid, I really bet a lot on it, but I'll share the logic and count on everyone's humility.

Hello.
It would be interesting to understand the logic of how you managed to reduce the number of possible keys.
Respect for your work.

[lordfrs]

my code is ready and running now for puzzle 66, but with 250,000 keys per second it will take 1 to 10 months  , I'm improving to have at least 1Mk/s, a dream would be 300Mk/s 

What is your code running on ? and is it on github?

is running in cuda c++ with a gtx 1650 4GB

Unfortunately I can't share the code yet, because as I said a few days ago, people with more resources or experience will find the keys and my work for months will have been in vain, I dedicated everything to this project and I am absolutely sure that This is the way.

skip screen prints in your code and focus only on the result, this will speed up you.

[james5000]

Let's go from the beginning so you can follow the reasoning.

when looking over and over all address from 1 to 65 i couldn't see anything that would help, obviously no pattern as we know,
So I simply asked my brother to look at me and yes! he managed to see the obvious, see how simple it is...

if you generate a private key with a reasonable size in the most random way you know, you will see that it will almost never, or even never, have standard characteristics as the friend mentioned on the previous page, such as:

0000, 1234, 4321, ffff.... right?

in the same way, it will be very difficult to have a few or many 1 bits, let's analyze the keys from 1 to 65:

Code:

    private key           bits zeros    bits ones

                 1             0           1
                 3             0           2
                 7             0           3
                 8             3           1
                15             3           2
                31             3           3
                4c             4           3
                e0             5           3
               1d3             3           6
               202             8           2
               483             7           4
               a7b             4           8
              1460             9           4
              2930             9           5
              68f3             6           9
              c936             8           8
             1764f             6          11
             3080d            12           6
             5749f             7          12
             d2c55            10          10
            1ba534            10          11
            2de40f            10          12
            556e52            11          12
            dc2a04            15           9
           1fa5ee5             8          17
           340326e            15          11
           6ac3875            13          14
           d916ce8            14          14
          17e2551e            13          16
          3d94cd64            14          16
          7d4fe747            10          21
          b862a62e            17          15
         1a96ca8d8            17          16
         34a65911d            18          16
         4aed21170            20          15
         9de820a7c            19          17
        1757756a93            15          22
        22382facd0            21          17
        4b5f8303e9            19          20
        e9ae4933d6            18          22
       153869acc5b            20          21
       2a221c58d8f            23          19
       6bd3b27c591            19          24
       e02b35a358f            22          22
      122fca143c05            26          19
      2ec18388d544            27          19
      6cd610b53cba            23          24
      ade6d7ce3b9b            17          31
     174176b015f4d            24          25
     22bd43c2e9354            26          24
     75070a1a009d4            32          19
     efae164cb9e3c            22          30
    180788e47e326c            29          24
    236fb6d5ad1f43            22          32
    6abe1f9b67e114            24          31
    9d18b63ac4ffdf            22          34
   1eb25c90795d61c            28          29
   2c675b852189a21            33          25
   7496cbb87cab44f            26          33
   fc07a1825367bbe            28          32
  13c96a3742f64906            32          29
  363d541eb611abee            28          34
  7cce5efdaccf6808            27          36
  f7051f27b09112d4            34          30
 1a838b13505b26867            36          29

it is very clear that the larger the interval the less chance that a key has too many or too few bits (if they are randomly generated, of course)
some keys even have the same number of bit 1 and bit 0 having an exact 50% rate.

let's say we're going to try 65, first we'd try ~50% right?
as it is odd let's assume it is 33 bits 0 and 32 bits 1, in the first interval would not be found, since we know the numbers of bit 1 and bit 0.

with a multi process we can search for the following ranges:
0 = 33 and 1 = 32
0 = 31 and 1 = 34
0 = 30 and 1 = 35
0 = 29 and 1 = 36
0 = 28 and 1 = 37

and their inverses

0 = 32 and 1 = 33
0 = 34 and 1 = 31
0 = 35 and 1 = 30
0 = 36 and 1 = 29
0 = 37 and 1 = 28

eliminating all other intervals that are very unlikely to be our much sought after key
66 is not too far from 65 with possible 1 and 0 bit intervals like:

0 = 33 and 1 = 33
0 = 32 and 1 = 34
0 = 31 and 1 = 35
0 = 30 and 1 = 36
0 = 29 and 1 = 37

and their inverses

0 = 33 and 1 = 33
0 = 34 and 1 = 32
0 = 35 and 1 = 31
0 = 36 and 1 = 30
0 = 37 and 1 = 29

It makes sense?

this is just a small start of what I got in about 2 months, I identified extra patterns, improved and adapted operations on the elliptic curve secp256k1 to speed up the search, but as I said I'm stuck at 250,000 key/s, I believe memory issues

help me to continue
1JamesJ2H2myei94NswaBATqEsBhATENSU

[james5000]

The time to fetch keys with these ranges eliminating keys with too few or too many bits would not be scalar, for example:

we suppose it took 1 second each character of a private key 0-9 a-f, ok?
a 2-digit key takes 16 times as long, so it would be 16 seconds

using this technique that I mentioned the time does not increase exponentially, as it was mentioned that if the 66 takes 1 year then the 67 would take 2 years, in fact the 67 would take a little more than a year, but not twice as much, since many combinations would be "excluded " of the search

i will post code later.

[albert0bsd]

It makes sense?

Yes it make sense.

i already about it on some telegram group but it have its owns complications for example iterating over the keys counting the number of bits an discarting some repetitive patters etc...

The main raeason that you get some slow speed is becuase (i bet) that you are using some scalar multiplications each time inestead of using Publickeys additions.

To be honest with you I still doubt about your times.. because even if you only test the 1% of the keys space that is still like 11 Thousand years:

Code:

>>> 2**65/1000000/60/60/24/365 * 0.01
11698.84834710144

0.5 % is near 5 thousand years, so in order to reach your target in 1 Single year you need to CHECK only 0.000085477 %

Code:

2**65/1000000/60/60/24/365 * 0.00000085477
0.9999824601651898

So now, you only need to proof mathtematically that you only need to check 0.000085477 %  of the range in order to achieve what you are saying.

And that is some kind of funny because if you only check those keys that ONLY have 33 bits in "1"  for puzzle 66 you need to check 9.94% or near 10% of the WHOLE RANGE

But repeat, the idea is good, just your calculations doesn't match with your expected time.

Regards

[james5000]

It makes sense?

Yes it make sense.

i already about it on some telegram group but it have its owns complications for example iterating over the keys counting the number of bits an discarting some repetitive patters etc...

The main raeason that you get some slow speed is becuase (i bet) that you are using some scalar multiplications each time inestead of using Publickeys additions.

To be honest with you I still doubt about your times.. because even if you only test the 1% of the keys space that is still like 11 Thousand years:

Code:

>>> 2**65/1000000/60/60/24/365 * 0.01
11698.84834710144

0.5 % is near 5 thousand years, so in order to reach your target in 1 Single year you need to CHECK only 0.000085477 %

Code:

2**65/1000000/60/60/24/365 * 0.00000085477
0.9999824601651898

So now, you only need to proof mathtematically that you only need to check 0.000085477 %  of the range in order to achieve what you are saying.

And that is some kind of funny because if you only check those keys that ONLY have 33 bits in "1"  for puzzle 66 you need to check 9.94% or near 10% of the WHOLE RANGE

But repeat, the idea is good, just your calculations doesn't match with your expected time.

Regards

your calculations are taking into account all possible combinations of puzzle 66, about having to skip some keys it is possible using a lexicographical search algorithm, it shifts the bits to the left keeping the amount of bit 0 and bit 1

I'm not deriving keys every iteration, I'm adding points, that's what's weird

[albert0bsd]

your calculations are taking into account all possible combinations of puzzle 66

Yes, i know that you are skipping some patters etc, lets to say that with that we can remove 66% of the whole keys, that reduce the 9.94% to some 3% and that is only for those keys with 33 bits in one "1" i am not considering all other combinations that you suggets like 32 bits in "1", 34 bits in "1" etc...

i mean just proof matematiically that you only need to test only 0.000085477 % of keys and i am going to belive you...

Numbers speak by itselfs

[james5000]

your calculations are taking into account all possible combinations of puzzle 66

Yes, i know that you are skipping some patters etc, lets to say that with that we can remove 66% of the whole keys, that reduce the 9.94% to some 3% and that is only for those keys with 33 bits in one "1" i am not considering all other combinations that you suggets like 32 bits in "1", 34 bits in "1" etc...

i mean just proof matematiically that you only need to test only 0.000085477 % of keys and i am going to belive you...

Numbers speak by itselfs

I sent an inbox, we can talk about it and I can show you why I exclude so many keys, The BSGS algorithm seems interesting to me, the speed is incredible

[zahid888]

Puzzle: 1        Zeros: 0        Ones: 1         Percent 0: 0.00%        Percent 1: 100.00%      Decimal: 1 | Binary: 1
Puzzle: 2        Zeros: 0        Ones: 2         Percent 0: 0.00%        Percent 1: 100.00%      Decimal: 3 | Binary: 11
Puzzle: 3        Zeros: 0        Ones: 3         Percent 0: 0.00%        Percent 1: 100.00%      Decimal: 7 | Binary: 111
Puzzle: 4        Zeros: 3        Ones: 1         Percent 0: 75.00%       Percent 1: 25.00%       Decimal: 8 | Binary: 1000
Puzzle: 5        Zeros: 2        Ones: 3         Percent 0: 40.00%       Percent 1: 60.00%       Decimal: 21 | Binary: 10101
Puzzle: 6        Zeros: 3        Ones: 3         Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 49 | Binary: 110001
Puzzle: 7        Zeros: 4        Ones: 3         Percent 0: 57.14%       Percent 1: 42.86%       Decimal: 76 | Binary: 1001100
Puzzle: 8        Zeros: 5        Ones: 3         Percent 0: 62.50%       Percent 1: 37.50%       Decimal: 224 | Binary: 11100000
Puzzle: 9        Zeros: 3        Ones: 6         Percent 0: 33.33%       Percent 1: 66.67%       Decimal: 467 | Binary: 111010011
Puzzle: 10       Zeros: 8        Ones: 2         Percent 0: 80.00%       Percent 1: 20.00%       Decimal: 514 | Binary: 1000000010
Puzzle: 11       Zeros: 7        Ones: 4         Percent 0: 63.64%       Percent 1: 36.36%       Decimal: 1155 | Binary: 10010000011
Puzzle: 12       Zeros: 4        Ones: 8         Percent 0: 33.33%       Percent 1: 66.67%       Decimal: 2683 | Binary: 101001111011
Puzzle: 13       Zeros: 9        Ones: 4         Percent 0: 69.23%       Percent 1: 30.77%       Decimal: 5216 | Binary: 1010001100000
Puzzle: 14       Zeros: 9        Ones: 5         Percent 0: 64.29%       Percent 1: 35.71%       Decimal: 10544 | Binary: 10100100110000
Puzzle: 15       Zeros: 6        Ones: 9         Percent 0: 40.00%       Percent 1: 60.00%       Decimal: 26867 | Binary: 110100011110011
Puzzle: 16       Zeros: 8        Ones: 8         Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 51510 | Binary: 1100100100110110
Puzzle: 17       Zeros: 6        Ones: 11        Percent 0: 35.29%       Percent 1: 64.71%       Decimal: 95823 | Binary: 10111011001001111
Puzzle: 18       Zeros: 12       Ones: 6         Percent 0: 66.67%       Percent 1: 33.33%       Decimal: 198669 | Binary: 110000100000001101
Puzzle: 19       Zeros: 7        Ones: 12        Percent 0: 36.84%       Percent 1: 63.16%       Decimal: 357535 | Binary: 1010111010010011111
Puzzle: 20       Zeros: 10       Ones: 10        Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 863317 | Binary: 11010010110001010101
Puzzle: 21       Zeros: 10       Ones: 11        Percent 0: 47.62%       Percent 1: 52.38%       Decimal: 1811764 | Binary: 110111010010100110100
Puzzle: 22       Zeros: 10       Ones: 12        Percent 0: 45.45%       Percent 1: 54.55%       Decimal: 3007503 | Binary: 1011011110010000001111
Puzzle: 23       Zeros: 11       Ones: 12        Percent 0: 47.83%       Percent 1: 52.17%       Decimal: 5598802 | Binary: 10101010110111001010010
Puzzle: 24       Zeros: 15       Ones: 9         Percent 0: 62.50%       Percent 1: 37.50%       Decimal: 14428676 | Binary: 110111000010101000000100
Puzzle: 25       Zeros: 8        Ones: 17        Percent 0: 32.00%       Percent 1: 68.00%       Decimal: 33185509 | Binary: 1111110100101111011100101
Puzzle: 26       Zeros: 15       Ones: 11        Percent 0: 57.69%       Percent 1: 42.31%       Decimal: 54538862 | Binary: 11010000000011001001101110
Puzzle: 27       Zeros: 13       Ones: 14        Percent 0: 48.15%       Percent 1: 51.85%       Decimal: 111949941 | Binary: 110101011000011100001110101
Puzzle: 28       Zeros: 14       Ones: 14        Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 227634408 | Binary: 1101100100010110110011101000
Puzzle: 29       Zeros: 13       Ones: 16        Percent 0: 44.83%       Percent 1: 55.17%       Decimal: 400708894 | Binary: 10111111000100101010100011110
Puzzle: 30       Zeros: 14       Ones: 16        Percent 0: 46.67%       Percent 1: 53.33%       Decimal: 1033162084 | Binary: 111101100101001100110101100100
Puzzle: 31       Zeros: 10       Ones: 21        Percent 0: 32.26%       Percent 1: 67.74%       Decimal: 2102388551 | Binary: 1111101010011111110011101000111
Puzzle: 32       Zeros: 17       Ones: 15        Percent 0: 53.12%       Percent 1: 46.88%       Decimal: 3093472814 | Binary: 10111000011000101010011000101110
Puzzle: 33       Zeros: 17       Ones: 16        Percent 0: 51.52%       Percent 1: 48.48%       Decimal: 7137437912 | Binary: 110101001011011001010100011011000
Puzzle: 34       Zeros: 18       Ones: 16        Percent 0: 52.94%       Percent 1: 47.06%       Decimal: 14133072157 | Binary: 1101001010011001011001000100011101
Puzzle: 35       Zeros: 20       Ones: 15        Percent 0: 57.14%       Percent 1: 42.86%       Decimal: 20112871792 | Binary: 10010101110110100100001000101110000
Puzzle: 36       Zeros: 19       Ones: 17        Percent 0: 52.78%       Percent 1: 47.22%       Decimal: 42387769980 | Binary: 100111011110100000100000101001111100
Puzzle: 37       Zeros: 15       Ones: 22        Percent 0: 40.54%       Percent 1: 59.46%       Decimal: 100251560595 | Binary: 1011101010111011101010110101010010011
Puzzle: 38       Zeros: 21       Ones: 17        Percent 0: 55.26%       Percent 1: 44.74%       Decimal: 146971536592 | Binary: 10001000111000001011111010110011010000
Puzzle: 39       Zeros: 19       Ones: 20        Percent 0: 48.72%       Percent 1: 51.28%       Decimal: 323724968937 | Binary: 100101101011111100000110000001111101001
Puzzle: 40       Zeros: 18       Ones: 22        Percent 0: 45.00%       Percent 1: 55.00%       Decimal: 1003651412950 | Binary: 1110100110101110010010010011001111010110
Puzzle: 41       Zeros: 20       Ones: 21        Percent 0: 48.78%       Percent 1: 51.22%       Decimal: 1458252205147 | Binary: 10101001110000110100110101100110001011011
Puzzle: 42       Zeros: 23       Ones: 19        Percent 0: 54.76%       Percent 1: 45.24%       Decimal: 2895374552463 | Binary: 101010001000100001110001011000110110001111
Puzzle: 43       Zeros: 19       Ones: 24        Percent 0: 44.19%       Percent 1: 55.81%       Decimal: 7409811047825 | Binary: 1101011110100111011001001111100010110010001
Puzzle: 44       Zeros: 22       Ones: 22        Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 15404761757071 | Binary: 11100000001010110011010110100011010110001111
Puzzle: 45       Zeros: 26       Ones: 19        Percent 0: 57.78%       Percent 1: 42.22%       Decimal: 19996463086597 | Binary: 100100010111111001010000101000011110000000101
Puzzle: 46       Zeros: 27       Ones: 19        Percent 0: 58.70%       Percent 1: 41.30%       Decimal: 51408670348612 | Binary: 1011101100000110000011100010001101010101000100
Puzzle: 47       Zeros: 23       Ones: 24        Percent 0: 48.94%       Percent 1: 51.06%       Decimal: 119666659114170 | Binary: 11011001101011000010000101101010011110010111010
Puzzle: 48       Zeros: 17       Ones: 31        Percent 0: 35.42%       Percent 1: 64.58%       Decimal: 191206974700443 | Binary: 101011011110011011010111110011100011101110011011
Puzzle: 49       Zeros: 24       Ones: 25        Percent 0: 48.98%       Percent 1: 51.02%       Decimal: 409118905032525 | Binary: 1011101000001011101101011000000010101111101001101
Puzzle: 50       Zeros: 26       Ones: 24        Percent 0: 52.00%       Percent 1: 48.00%       Decimal: 611140496167764 | Binary: 10001010111101010000111100001011101001001101010100
Puzzle: 51       Zeros: 32       Ones: 19        Percent 0: 62.75%       Percent 1: 37.25%       Decimal: 2058769515153876 | Binary: 111010100000111000010100001101000000000100111010100
Puzzle: 52       Zeros: 22       Ones: 30        Percent 0: 42.31%       Percent 1: 57.69%       Decimal: 4216495639600700 | Binary: 1110111110101110000101100100110010111001111000111100
Puzzle: 53       Zeros: 29       Ones: 24        Percent 0: 54.72%       Percent 1: 45.28%       Decimal: 6763683971478124 | Binary: 11000000001111000100011100100011111100011001001101100
Puzzle: 54       Zeros: 22       Ones: 32        Percent 0: 40.74%       Percent 1: 59.26%       Decimal: 9974455244496707 | Binary: 100011011011111011011011010101101011010001111101000011
Puzzle: 55       Zeros: 24       Ones: 31        Percent 0: 43.64%       Percent 1: 56.36%       Decimal: 30045390491869460 | Binary: 1101010101111100001111110011011011001111110000100010100
Puzzle: 56       Zeros: 22       Ones: 34        Percent 0: 39.29%       Percent 1: 60.71%       Decimal: 44218742292676575 | Binary: 10011101000110001011011000111010110001001111111111011111
Puzzle: 57       Zeros: 28       Ones: 29        Percent 0: 49.12%       Percent 1: 50.88%       Decimal: 138245758910846492 | Binary: 111101011001001011100100100000111100101011101011000011100
Puzzle: 58       Zeros: 33       Ones: 25        Percent 0: 56.90%       Percent 1: 43.10%       Decimal: 199976667976342049 | Binary: 1011000110011101011011100001010010000110001001101000100001
Puzzle: 59       Zeros: 26       Ones: 33        Percent 0: 44.07%       Percent 1: 55.93%       Decimal: 525070384258266191 | Binary: 11101001001011011001011101110000111110010101011010001001111
Puzzle: 60       Zeros: 28       Ones: 32        Percent 0: 46.67%       Percent 1: 53.33%       Decimal: 1135041350219496382 | Binary: 111111000000011110100001100000100101001101100111101110111110
Puzzle: 61       Zeros: 32       Ones: 29        Percent 0: 52.46%       Percent 1: 47.54%       Decimal: 1425787542618654982 | Binary: 1001111001001011010100011011101000010111101100100100100000110
Puzzle: 62       Zeros: 28       Ones: 34        Percent 0: 45.16%       Percent 1: 54.84%       Decimal: 3908372542507822062 | Binary: 11011000111101010101000001111010110110000100011010101111101110
Puzzle: 63       Zeros: 27       Ones: 36        Percent 0: 42.86%       Percent 1: 57.14%       Decimal: 8993229949524469768 | Binary: 111110011001110010111101111110110101100110011110110100000001000
Puzzle: 64       Zeros: 34       Ones: 30        Percent 0: 53.12%       Percent 1: 46.88%       Decimal: 17799667357578236628 | Binary: 1111011100000101000111110010011110110000100100010001001011010100
Puzzle: 65       Zeros: 36       Ones: 29        Percent 0: 55.38%       Percent 1: 44.62%       Decimal: 30568377312064202855 | Binary: 11010100000111000101100010011010100000101101100100110100001100111

The most challenging task in the world is to guess a random number

[james5000]

Puzzle: 1        Zeros: 0        Ones: 1         Percent 0: 0.00%        Percent 1: 100.00%      Decimal: 1 | Binary: 1
Puzzle: 2        Zeros: 0        Ones: 2         Percent 0: 0.00%        Percent 1: 100.00%      Decimal: 3 | Binary: 11
Puzzle: 3        Zeros: 0        Ones: 3         Percent 0: 0.00%        Percent 1: 100.00%      Decimal: 7 | Binary: 111
Puzzle: 4        Zeros: 3        Ones: 1         Percent 0: 75.00%       Percent 1: 25.00%       Decimal: 8 | Binary: 1000
Puzzle: 5        Zeros: 2        Ones: 3         Percent 0: 40.00%       Percent 1: 60.00%       Decimal: 21 | Binary: 10101
Puzzle: 6        Zeros: 3        Ones: 3         Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 49 | Binary: 110001
Puzzle: 7        Zeros: 4        Ones: 3         Percent 0: 57.14%       Percent 1: 42.86%       Decimal: 76 | Binary: 1001100
Puzzle: 8        Zeros: 5        Ones: 3         Percent 0: 62.50%       Percent 1: 37.50%       Decimal: 224 | Binary: 11100000
Puzzle: 9        Zeros: 3        Ones: 6         Percent 0: 33.33%       Percent 1: 66.67%       Decimal: 467 | Binary: 111010011
Puzzle: 10       Zeros: 8        Ones: 2         Percent 0: 80.00%       Percent 1: 20.00%       Decimal: 514 | Binary: 1000000010
Puzzle: 11       Zeros: 7        Ones: 4         Percent 0: 63.64%       Percent 1: 36.36%       Decimal: 1155 | Binary: 10010000011
Puzzle: 12       Zeros: 4        Ones: 8         Percent 0: 33.33%       Percent 1: 66.67%       Decimal: 2683 | Binary: 101001111011
Puzzle: 13       Zeros: 9        Ones: 4         Percent 0: 69.23%       Percent 1: 30.77%       Decimal: 5216 | Binary: 1010001100000
Puzzle: 14       Zeros: 9        Ones: 5         Percent 0: 64.29%       Percent 1: 35.71%       Decimal: 10544 | Binary: 10100100110000
Puzzle: 15       Zeros: 6        Ones: 9         Percent 0: 40.00%       Percent 1: 60.00%       Decimal: 26867 | Binary: 110100011110011
Puzzle: 16       Zeros: 8        Ones: 8         Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 51510 | Binary: 1100100100110110
Puzzle: 17       Zeros: 6        Ones: 11        Percent 0: 35.29%       Percent 1: 64.71%       Decimal: 95823 | Binary: 10111011001001111
Puzzle: 18       Zeros: 12       Ones: 6         Percent 0: 66.67%       Percent 1: 33.33%       Decimal: 198669 | Binary: 110000100000001101
Puzzle: 19       Zeros: 7        Ones: 12        Percent 0: 36.84%       Percent 1: 63.16%       Decimal: 357535 | Binary: 1010111010010011111
Puzzle: 20       Zeros: 10       Ones: 10        Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 863317 | Binary: 11010010110001010101
Puzzle: 21       Zeros: 10       Ones: 11        Percent 0: 47.62%       Percent 1: 52.38%       Decimal: 1811764 | Binary: 110111010010100110100
Puzzle: 22       Zeros: 10       Ones: 12        Percent 0: 45.45%       Percent 1: 54.55%       Decimal: 3007503 | Binary: 1011011110010000001111
Puzzle: 23       Zeros: 11       Ones: 12        Percent 0: 47.83%       Percent 1: 52.17%       Decimal: 5598802 | Binary: 10101010110111001010010
Puzzle: 24       Zeros: 15       Ones: 9         Percent 0: 62.50%       Percent 1: 37.50%       Decimal: 14428676 | Binary: 110111000010101000000100
Puzzle: 25       Zeros: 8        Ones: 17        Percent 0: 32.00%       Percent 1: 68.00%       Decimal: 33185509 | Binary: 1111110100101111011100101
Puzzle: 26       Zeros: 15       Ones: 11        Percent 0: 57.69%       Percent 1: 42.31%       Decimal: 54538862 | Binary: 11010000000011001001101110
Puzzle: 27       Zeros: 13       Ones: 14        Percent 0: 48.15%       Percent 1: 51.85%       Decimal: 111949941 | Binary: 110101011000011100001110101
Puzzle: 28       Zeros: 14       Ones: 14        Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 227634408 | Binary: 1101100100010110110011101000
Puzzle: 29       Zeros: 13       Ones: 16        Percent 0: 44.83%       Percent 1: 55.17%       Decimal: 400708894 | Binary: 10111111000100101010100011110
Puzzle: 30       Zeros: 14       Ones: 16        Percent 0: 46.67%       Percent 1: 53.33%       Decimal: 1033162084 | Binary: 111101100101001100110101100100
Puzzle: 31       Zeros: 10       Ones: 21        Percent 0: 32.26%       Percent 1: 67.74%       Decimal: 2102388551 | Binary: 1111101010011111110011101000111
Puzzle: 32       Zeros: 17       Ones: 15        Percent 0: 53.12%       Percent 1: 46.88%       Decimal: 3093472814 | Binary: 10111000011000101010011000101110
Puzzle: 33       Zeros: 17       Ones: 16        Percent 0: 51.52%       Percent 1: 48.48%       Decimal: 7137437912 | Binary: 110101001011011001010100011011000
Puzzle: 34       Zeros: 18       Ones: 16        Percent 0: 52.94%       Percent 1: 47.06%       Decimal: 14133072157 | Binary: 1101001010011001011001000100011101
Puzzle: 35       Zeros: 20       Ones: 15        Percent 0: 57.14%       Percent 1: 42.86%       Decimal: 20112871792 | Binary: 10010101110110100100001000101110000
Puzzle: 36       Zeros: 19       Ones: 17        Percent 0: 52.78%       Percent 1: 47.22%       Decimal: 42387769980 | Binary: 100111011110100000100000101001111100
Puzzle: 37       Zeros: 15       Ones: 22        Percent 0: 40.54%       Percent 1: 59.46%       Decimal: 100251560595 | Binary: 1011101010111011101010110101010010011
Puzzle: 38       Zeros: 21       Ones: 17        Percent 0: 55.26%       Percent 1: 44.74%       Decimal: 146971536592 | Binary: 10001000111000001011111010110011010000
Puzzle: 39       Zeros: 19       Ones: 20        Percent 0: 48.72%       Percent 1: 51.28%       Decimal: 323724968937 | Binary: 100101101011111100000110000001111101001
Puzzle: 40       Zeros: 18       Ones: 22        Percent 0: 45.00%       Percent 1: 55.00%       Decimal: 1003651412950 | Binary: 1110100110101110010010010011001111010110
Puzzle: 41       Zeros: 20       Ones: 21        Percent 0: 48.78%       Percent 1: 51.22%       Decimal: 1458252205147 | Binary: 10101001110000110100110101100110001011011
Puzzle: 42       Zeros: 23       Ones: 19        Percent 0: 54.76%       Percent 1: 45.24%       Decimal: 2895374552463 | Binary: 101010001000100001110001011000110110001111
Puzzle: 43       Zeros: 19       Ones: 24        Percent 0: 44.19%       Percent 1: 55.81%       Decimal: 7409811047825 | Binary: 1101011110100111011001001111100010110010001
Puzzle: 44       Zeros: 22       Ones: 22        Percent 0: 50.00%       Percent 1: 50.00%       Decimal: 15404761757071 | Binary: 11100000001010110011010110100011010110001111
Puzzle: 45       Zeros: 26       Ones: 19        Percent 0: 57.78%       Percent 1: 42.22%       Decimal: 19996463086597 | Binary: 100100010111111001010000101000011110000000101
Puzzle: 46       Zeros: 27       Ones: 19        Percent 0: 58.70%       Percent 1: 41.30%       Decimal: 51408670348612 | Binary: 1011101100000110000011100010001101010101000100
Puzzle: 47       Zeros: 23       Ones: 24        Percent 0: 48.94%       Percent 1: 51.06%       Decimal: 119666659114170 | Binary: 11011001101011000010000101101010011110010111010
Puzzle: 48       Zeros: 17       Ones: 31        Percent 0: 35.42%       Percent 1: 64.58%       Decimal: 191206974700443 | Binary: 101011011110011011010111110011100011101110011011
Puzzle: 49       Zeros: 24       Ones: 25        Percent 0: 48.98%       Percent 1: 51.02%       Decimal: 409118905032525 | Binary: 1011101000001011101101011000000010101111101001101
Puzzle: 50       Zeros: 26       Ones: 24        Percent 0: 52.00%       Percent 1: 48.00%       Decimal: 611140496167764 | Binary: 10001010111101010000111100001011101001001101010100
Puzzle: 51       Zeros: 32       Ones: 19        Percent 0: 62.75%       Percent 1: 37.25%       Decimal: 2058769515153876 | Binary: 111010100000111000010100001101000000000100111010100
Puzzle: 52       Zeros: 22       Ones: 30        Percent 0: 42.31%       Percent 1: 57.69%       Decimal: 4216495639600700 | Binary: 1110111110101110000101100100110010111001111000111100
Puzzle: 53       Zeros: 29       Ones: 24        Percent 0: 54.72%       Percent 1: 45.28%       Decimal: 6763683971478124 | Binary: 11000000001111000100011100100011111100011001001101100
Puzzle: 54       Zeros: 22       Ones: 32        Percent 0: 40.74%       Percent 1: 59.26%       Decimal: 9974455244496707 | Binary: 100011011011111011011011010101101011010001111101000011
Puzzle: 55       Zeros: 24       Ones: 31        Percent 0: 43.64%       Percent 1: 56.36%       Decimal: 30045390491869460 | Binary: 1101010101111100001111110011011011001111110000100010100
Puzzle: 56       Zeros: 22       Ones: 34        Percent 0: 39.29%       Percent 1: 60.71%       Decimal: 44218742292676575 | Binary: 10011101000110001011011000111010110001001111111111011111
Puzzle: 57       Zeros: 28       Ones: 29        Percent 0: 49.12%       Percent 1: 50.88%       Decimal: 138245758910846492 | Binary: 111101011001001011100100100000111100101011101011000011100
Puzzle: 58       Zeros: 33       Ones: 25        Percent 0: 56.90%       Percent 1: 43.10%       Decimal: 199976667976342049 | Binary: 1011000110011101011011100001010010000110001001101000100001
Puzzle: 59       Zeros: 26       Ones: 33        Percent 0: 44.07%       Percent 1: 55.93%       Decimal: 525070384258266191 | Binary: 11101001001011011001011101110000111110010101011010001001111
Puzzle: 60       Zeros: 28       Ones: 32        Percent 0: 46.67%       Percent 1: 53.33%       Decimal: 1135041350219496382 | Binary: 111111000000011110100001100000100101001101100111101110111110
Puzzle: 61       Zeros: 32       Ones: 29        Percent 0: 52.46%       Percent 1: 47.54%       Decimal: 1425787542618654982 | Binary: 1001111001001011010100011011101000010111101100100100100000110
Puzzle: 62       Zeros: 28       Ones: 34        Percent 0: 45.16%       Percent 1: 54.84%       Decimal: 3908372542507822062 | Binary: 11011000111101010101000001111010110110000100011010101111101110
Puzzle: 63       Zeros: 27       Ones: 36        Percent 0: 42.86%       Percent 1: 57.14%       Decimal: 8993229949524469768 | Binary: 111110011001110010111101111110110101100110011110110100000001000
Puzzle: 64       Zeros: 34       Ones: 30        Percent 0: 53.12%       Percent 1: 46.88%       Decimal: 17799667357578236628 | Binary: 1111011100000101000111110010011110110000100100010001001011010100
Puzzle: 65       Zeros: 36       Ones: 29        Percent 0: 55.38%       Percent 1: 44.62%       Decimal: 30568377312064202855 | Binary: 11010100000111000101100010011010100000101101100100110100001100111

The most challenging task in the world is to guess a random number

The problem isn't guessing a random number, it's narrowing down the search range to more probable keys. Thank you for posting the percentages; this way we can see that after 54, none have fewer than 40% of bits as 1 or 0, nor more than 60%. I believe we can accept this as a fact.

[frozenen]

james5000 Your reduction method makes sense and I agree the private key will conform to the similar ratio of 1 and 0 in binary but what I don't understand is how your app searches, is your app reducing the ranges then search every address in that? or does it only search keys that conform to the binary ratio? For example can you put a start and end range and then it skips keys that don't conform? When are you planning to release your app even just the CPU version?