Bitcoin puzzle transaction ~32 BTC prize to who solves it

[zahid888]

Whoever manages to obtain the private key for Puzzle 66.
Is requested to encrypt it using this script and post the encrypted message here. Post only the encrypted message, and keep the salt and password to yourself.
Then, proceed to complete your transaction process after few days. If, for any reason, the transaction fails to validate and someone else hijacks it,
You are encouraged to post your salt and password here as evidence that you had solved Puzzle 66.
This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.
@alberto or any other member, if you discover any vulnerabilities here or are capable of cracking this script, please inform us. Additionally, if there are any alternative implementations, kindly share those as well.

Just the first person who solves Puzzle 66 issues the first 32 bytes + 32 bytes of the public key and replaces it with ***********
example:   023b1ac48deb1302bbc9bd302104e6747**************************
The first person who solves Puzzle 66  can post it in this thread or a YouTube video... record the time

It can prove that he is the first person to discover the private key of Puzzle 66... ​​and transfer 6.6 BTC away the next day...
But of course thousands of programs will leak the public key within 1 minute after the transaction, and snatch this bonus
No one Really legal possession....
Even the creator saatoshi_rising cannot sue because he has already released the BTC ...as game bonuses

This is also a good idea, but when you publicly post either the beginning or the end part of the 32-bit public key of puzzle 66, I am completely sure that Satoshi himself will sweep puzzle 66 .. just like he has done with puzzle 120 and puzzle 125.. and he has not even spent those coins yet, which proves that he has done it,, but if we post a lot of encrypted messages in which fake and real are mixed,, then Satoshi will not even know, and after the public key is exposed, it will be known who has posted the real key.
Whether someone does it or not, I am definitely going to do it. I have scanned 12% so far, but if luck doesn't support us, what can we do? I am telling everyone to do this because I am very curious to see this process, and conducting this process silently would only perpetuate confusion surrounding the issue forever.

[kTimesG]

You are encouraged to post your salt and password here as evidence that you had solved Puzzle 66.
This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.
@alberto or any other member, if you discover any vulnerabilities here or are capable of cracking this script, please inform us. Additionally, if there are any alternative implementations, kindly share those as well.

Why not simply AES-256 encrypt the private key and be done with it in, like, 3 lines? No password hashing and so on.

I solved puzzle #66 but I'm very afraid to sweep it. Since no one claimed it yet, they definitely belong to me, right? Here's my proof: the encrypted private key is:

Code:

0x4074a46512e55c9559cb8af86c983bc424d9f2d5fbb3c14b65b1045d21972d219b359a24806826a94c72e9a95ca00dab

First 16 bytes are the IV, then 32 bytes of private key. I removed the padding, since it's 16 bytes of 0x10 (e.g. no bytes in last block).

If anyone steals my prize I will divulge the decryption key.

Or, simply hash it once together with some secret value, you only need to prove you knew the hashed value before anyone else, not to protect the actual data.

Code:

SHA256(privateKey + "some secret value")

[zahid888]

Code:

SHA256(privateKey + "some secret value")

Truly, this turned out to be an incredibly straightforward process;Lol:D I realize that I was needlessly complicating things. That's the true advantage of sharing whatever thoughts occupy your mind—people make it more easier.   Thanks
I receive numerous messages in my inbox from individuals who are diligently attempting to solve Puzzle 66 and choose to share their ideas with me. However, I've noticed that not a single post from them exists within the community. I would advise them to come here and share their ideas; doing so will undoubtedly be beneficial for them.
Edit:
In the midst of our conversation, another thought crosses my mind: why not explore the another crude measuring instrument, of the hashing strength of the community within a 66-bit range?  Hence, this is the SHA256 hash: '7e4cb2ad57ba006e5991ad3289b51744ee2d1a02812905a0b64f17c22d978ce0', In bitrange '20000000000000000:40000000000000000', where the puzzle 66 private key exists in hexadecimal format with leading '0x', without any additional text or message or password. (Something valuable is hidden here)... In my opinion, hashing alone might be an exceptionally fast process, potentially solvable in matter of few minutes ??
Something like this...

Code:

import hashlib
target = '7e4cb2ad57ba006e5991ad3289b51744ee2d1a02812905a0b64f17c22d978ce0'
for i in range (2**65,2**66):
 key = hex(i)
 sha = hashlib.sha256(key.encode()).hexdigest()
 if sha == target:
  print("\nfound",key, sha)
  break
 else:
  print(key, sha, end='\r')

[albert0bsd]

Why not simply AES-256 encrypt the private key and be done with it in, like, 3 lines? No password hashing and so on.

I solved puzzle #66 but I'm very afraid to sweep it. Since no one claimed it yet, they definitely belong to me, right? Here's my proof: the encrypted private key is:

Code:

0x4074a46512e55c9559cb8af86c983bc424d9f2d5fbb3c14b65b1045d21972d219b359a24806826a94c72e9a95ca00dab

First 16 bytes are the IV, then 32 bytes of private key. I removed the padding, since it's 16 bytes of 0x10 (e.g. no bytes in last block).

Quoted to save this

If anyone steals my prize I will divulge the decryption key.

But why? I mean what you want to achieve with this?

[citb0in]

If anyone steals my prize I will divulge the decryption key.

but that's a funny threat if someone steals your price, then he has already stolen it and therefore the pubkey is known and anyone can calculate the private key within seconds. Moreover, it would be made public here immediately. But that doesn't change the fact that your prize has still been snatched by someone else.

But I'm sure (no, I know) that you don't know the private key of #66 yet. 

[kTimesG]

If anyone steals my prize I will divulge the decryption key.

But why? I mean what you want to achieve with this?

It's funny that you didn't see anything wrong there I missed the part that we also need 16 bytes for the encrypted padding block, or else we can put whatever we want in it.

but that's a funny threat if someone steals your price, then he has already stolen it and therefore the pubkey is known and anyone can calculate the private key within seconds. Moreover, it would be made public here immediately. But that doesn't change the fact that your prize has still been snatched by someone else.

But I'm sure (no, I know) that you don't know the private key of #66 yet.  

I'm not even bothering with it, as I said already that the ROI on it is close to 0 as it's a higher fees competition. Any number above 0 of free bitcoin is better than 0, so no one will stop at some lower bound.

And the other problem is that you don't even need some powerful GPU to solve the 66 priv key once pub is known. Most of the work can be done in advance.

[JavaSandcrawler]

I receive numerous messages in my inbox from individuals who are diligently attempting to solve Puzzle 66 and choose to share their ideas with me. However, I've noticed that not a single post from them exists within the community. I would advise them to come here and share their ideas; doing so will undoubtedly be beneficial for them.

Hi all. In principle, I didn’t plan to write here, I’ll just write as a participant. I've been working on the solution for about two years. this year I found ~2000 prefixes 13zb1hQbW.
13zb1hQbWV 50 pieces.
13zb1hQbWVs 2 pieces.
This is probably very stupid, but I'm just keeping it as a journal.

There were a lot of ideas, and a lot of wasted time. I also tortured the IBM quantum machine and got some research results.
But I still haven’t solved 66.
At the moment I can quickly iterate through 2xxxx000000000000:2xxxxffffffffffff

If user kTimesG really solved 66, then I sincerely congratulate him. I planned that if someone finds the key, then I will not try to open the next keys, because firstly, the range is much larger, and secondly, there will also be sharks hungry for easy money from the public key. But the problem with sharks is really very big. I did research on some addresses. Perhaps the right solution would be to block these funds. So that no one gets it.

Also please forgive me, I am using a translator.

[citb0in]

I've been working on the solution for about two years. this year I found ~2000 prefixes 13zb1hQbW.
13zb1hQbWV 50 pieces.
13zb1hQbWVs 2 pieces.
This is probably very stupid, but ...

Yes, absolutely!  That IS stupid. I don't understand why so many people in here insist and keep trying to find similar strings whose hash value only approximates the target hash value. This is a pure waste of time, nerves and resources as it does not contribute in any way - not even in the slightest - to speeding up or even impairing the solution finding process.

The following two strings demonstrate the avalanche effect. Even if you add the punctuation "." at the end of the sentence and thus changing the string slightly, it'll produce a complete different hash.

This is stupid
f061b6de6d36df2330b1ba15dca3cf858c7e20a2935e453668c6b7124e58d80b

This is stupid.
dbf61110bee7b482f8b5536d4996effaae1de69fcd5e132c0d3af1ebf7146b3d

Imagine you find the string of the hash f061b6de6d36df2330b1ba15dca3cf858c7e20a2935e453668c6b7124e58d80b
f061b6de6d36df2330b1ba15dca3cf858c7e20a2935e453668c6b7124e58d80c

never ever it will be similar to the real string "This is stupid". The string for this hash could be "something completely different in ch4rs and s!ze"

Please stop looking for prefixes, suffixes or parts of hashes because it's a waste of time. Instead, invest your strength and energy and read about the avalanche effect.

There were a lot of ideas, and a lot of wasted time. I also tortured the IBM quantum machine and got some research results.

So true ...

But I still haven’t solved 66.

puzzled? no, huh?

Also please forgive me, I am using a translator.

anyone's welcome here despite of their origin and native language. Have fun and enjoy and last but not least ... Good luck!
Cheers

[paniker]

Hi, citb0in! i think stupid you are, because  JavaSandcrawler  sad nothing about hashing, only prefs, why he collecting them you don't know.

I've been working on the solution for about two years. this year I found ~2000 prefixes 13zb1hQbW.
13zb1hQbWV 50 pieces.
13zb1hQbWVs 2 pieces.
This is probably very stupid, but ...

Yes, absolutely!  That IS stupid. I don't understand why so many people in here insist and keep trying to find similar strings whose hash value only approximates the target hash value. This is a pure waste of time, nerves and resources as it does not contribute in any way - not even in the slightest - to speeding up or even impairing the solution finding process.

The following two strings demonstrate the avalanche effect. Even if you add the punctuation "." at the end of the sentence and thus changing the string slightly, it'll produce a complete different hash.

This is stupid
f061b6de6d36df2330b1ba15dca3cf858c7e20a2935e453668c6b7124e58d80b

This is stupid.
dbf61110bee7b482f8b5536d4996effaae1de69fcd5e132c0d3af1ebf7146b3d

Imagine you find the string of the hash f061b6de6d36df2330b1ba15dca3cf858c7e20a2935e453668c6b7124e58d80b
f061b6de6d36df2330b1ba15dca3cf858c7e20a2935e453668c6b7124e58d80c

never ever it will be similar to the real string "This is stupid". The string for this hash could be "something completely different in ch4rs and s!ze"

Please stop looking for prefixes, suffixes or parts of hashes because it's a waste of time. Instead, invest your strength and energy and read about the avalanche effect.

There were a lot of ideas, and a lot of wasted time. I also tortured the IBM quantum machine and got some research results.

So true ...

But I still haven’t solved 66.

puzzled? no, huh?

Also please forgive me, I am using a translator.

anyone's welcome here despite of their origin and native language. Have fun and enjoy and last but not least ... Good luck!
Cheers

The following two strings demonstrate the avalanche effect - you got a range, very huge yeh, but it's a range anyway, so yuor effect got a start and got an and.
he show 2 pref with WVs, nice if you ask math you got something like that 2^65 / 58^10 ~ 85 - 13zb1hQbWVs

so where is here you avalanche effect could be?

[JavaSandcrawler]

Hi, citb0in! i think stupid you are, because  JavaSandcrawler  sad nothing about hashing, only prefs, why he collecting them you don't know.

I collect them like a journal. For example: I want to search in 123000-124000, I open the journal and see that I have already gone to 123444.

Also, based on what I found, I have a code in Java using AI, which, based on the first 20-30 bits, selects similar ones and gives me ranges.
For example, I found some kind of prefix 13zb1hQbW in 1 minute. And I have about 500 of these using the code.

In addition, I have some experience using the 8-bit binary table. In which I saw an interesting pattern on previous addresses.

I did a lot of research with hashes, mersen twister, random number libraries and others ideias... And i once even raised my network, with the very first vulnerabilities, lol.
This turned into an interesting learning experience for me.

[brainless]

I receive numerous messages in my inbox from individuals who are diligently attempting to solve Puzzle 66 and choose to share their ideas with me. However, I've noticed that not a single post from them exists within the community. I would advise them to come here and share their ideas; doing so will undoubtedly be beneficial for them.

Hi all. In principle, I didn’t plan to write here, I’ll just write as a participant. I've been working on the solution for about two years. this year I found ~2000 prefixes 13zb1hQbW.
13zb1hQbWV 50 pieces.
13zb1hQbWVs 2 pieces.
This is probably very stupid, but I'm just keeping it as a journal.

There were a lot of ideas, and a lot of wasted time. I also tortured the IBM quantum machine and got some research results.
But I still haven’t solved 66.
At the moment I can quickly iterate through 2xxxx000000000000:2xxxxffffffffffff

If user kTimesG really solved 66, then I sincerely congratulate him. I planned that if someone finds the key, then I will not try to open the next keys, because firstly, the range is much larger, and secondly, there will also be sharks hungry for easy money from the public key. But the problem with sharks is really very big. I did research on some addresses. Perhaps the right solution would be to block these funds. So that no one gets it.

Also please forgive me, I am using a translator.

Could you Post your finding prefixes 13zb1hQbW here in text files or upload at some download able link ?

[nomachine]

But I'm sure (no, I know) that you don't know the private key of #66 yet. 

I would hire some block solvers here right away.   

[jacky19790729]

13zb1hQbWV 50 pieces.
13zb1hQbWVs 2 pieces.

13zb1hQbWV  10 char match in ripemd160 hash will be  little reference significance
#0x20000000000000000 ~ 0x40000000000000000 have  10000+  private key has  10 char match compressed address

13zb1hQbWVs  11 char match
#0x20000000000000000 ~ 0x40000000000000000 have  200~250  private key has  11 char match compressed address

13zb1hQbWVsc  12 char match 
#0x20000000000000000 ~ 0x40000000000000000 have 3~4  private key has  12 char match compressed address

I found 13zb1hQbWVsSAaNvpKfmc43NsuAj33LyRM in range 0x20000000000000000 ~ 0x40000000000000000  last month
But I still don't know which range I should jump and keep search

[JavaSandcrawler]

Could you Post your finding prefixes 13zb1hQbW here in text files or upload at some download able link ?

I already shared some list. Have already appeared here. So I'm sorry I can't

I found 13zb1hQbWVsSAaNvpKfmc43NsuAj33LyRM in range 0x20000000000000000 ~ 0x40000000000000000  last month
But I still don't know which range I should jump and keep search

Send me PM pls. I can share 1 WVs if u share too. This of course doesn't make sense lol

[zahid888]

13zb1hQbWV 50 pieces.
13zb1hQbWVs 2 pieces.

13zb1hQbWV  10 char match in ripemd160 hash will be  little reference significance
#0x20000000000000000 ~ 0x40000000000000000 have  10000+  private key has  10 char match compressed address

13zb1hQbWVs  11 char match
#0x20000000000000000 ~ 0x40000000000000000 have  200~250  private key has  11 char match compressed address

13zb1hQbWVsc  12 char match  
#0x20000000000000000 ~ 0x40000000000000000 have 3~4  private key has  12 char match compressed address

I found 13zb1hQbWVsSAaNvpKfmc43NsuAj33LyRM in range 0x20000000000000000 ~ 0x40000000000000000  last month
But I still don't know which range I should jump and keep search

Are you sure about this? Where did you get this information from? Will you share the source of this information?

Hi all. In principle, I didn’t plan to write here, I’ll just write as a participant.

You are welcome bro

[kTimesG]

13zb1hQbWV  10 char match in ripemd160 hash will be  little reference significance
#0x20000000000000000 ~ 0x40000000000000000 have  10000+  private key has  10 char match compressed address

13zb1hQbWVs  11 char match
#0x20000000000000000 ~ 0x40000000000000000 have  200~250  private key has  11 char match compressed address

13zb1hQbWVsc  12 char match  
#0x20000000000000000 ~ 0x40000000000000000 have 3~4  private key has  12 char match compressed address

I found 13zb1hQbWVsSAaNvpKfmc43NsuAj33LyRM in range 0x20000000000000000 ~ 0x40000000000000000  last month
But I still don't know which range I should jump and keep search

Are you saying you found 10000+ private keys in the 65-bit range with all of them sharing that exact 10-char prefix? So, in other words, 10000+ hashes with same 59-bit prefix in a 65-bit keyspace? And hundreds of keys with same 64.43 bits of hash prefix in a 65-bit keyspace? This smells like "not even remotely possible".

[snaz3d]

Hi, citb0in! i think stupid you are, because  JavaSandcrawler  sad nothing about hashing, only prefs, why he collecting them you don't know.

I collect them like a journal. For example: I want to search in 123000-124000, I open the journal and see that I have already gone to 123444.

Also, based on what I found, I have a code in Java using AI, which, based on the first 20-30 bits, selects similar ones and gives me ranges.
For example, I found some kind of prefix 13zb1hQbW in 1 minute. And I have about 500 of these using the code.

In addition, I have some experience using the 8-bit binary table. In which I saw an interesting pattern on previous addresses.

I did a lot of research with hashes, mersen twister, random number libraries and others ideias... And i once even raised my network, with the very first vulnerabilities, lol.
This turned into an interesting learning experience for me.

There is no pattern.

[JavaSandcrawler]

There is no pattern.

https://i.postimg.cc/1XR5swQv/photo-2024-02-06-20-12-03.jpg

[zahid888]

There is no pattern.

Does that mean you just pressed CTRL+F and searched for '11', and a pattern like this appeared? Am I right? seems interesting

[pbies]

Code:

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

###

Code:

00000000000000000000000000000000000000000000000000000000000000001
00000000000000000000000000000000000000000000000000000000000000011
00000000000000000000000000000000000000000000000000000000000000111
00000000000000000000000000000000000000000000000000000000000001000
00000000000000000000000000000000000000000000000000000000000010101
00000000000000000000000000000000000000000000000000000000000110001
00000000000000000000000000000000000000000000000000000000001001100
00000000000000000000000000000000000000000000000000000000011100000
00000000000000000000000000000000000000000000000000000000111010011
00000000000000000000000000000000000000000000000000000001000000010
00000000000000000000000000000000000000000000000000000010010000011
00000000000000000000000000000000000000000000000000000101001111011
00000000000000000000000000000000000000000000000000001010001100000
00000000000000000000000000000000000000000000000000010100100110000
00000000000000000000000000000000000000000000000000110100011110011
00000000000000000000000000000000000000000000000001100100100110110
00000000000000000000000000000000000000000000000010111011001001111
00000000000000000000000000000000000000000000000110000100000001101
00000000000000000000000000000000000000000000001010111010010011111
00000000000000000000000000000000000000000000011010010110001010101
00000000000000000000000000000000000000000000110111010010100110100
00000000000000000000000000000000000000000001011011110010000001111
00000000000000000000000000000000000000000010101010110111001010010
00000000000000000000000000000000000000000110111000010101000000100
00000000000000000000000000000000000000001111110100101111011100101
00000000000000000000000000000000000000011010000000011001001101110
00000000000000000000000000000000000000110101011000011100001110101
00000000000000000000000000000000000001101100100010110110011101000
00000000000000000000000000000000000010111111000100101010100011110
00000000000000000000000000000000000111101100101001100110101100100
00000000000000000000000000000000001111101010011111110011101000111
00000000000000000000000000000000010111000011000101010011000101110
00000000000000000000000000000000110101001011011001010100011011000
00000000000000000000000000000001101001010011001011001000100011101
00000000000000000000000000000010010101110110100100001000101110000
00000000000000000000000000000100111011110100000100000101001111100
00000000000000000000000000001011101010111011101010110101010010011
00000000000000000000000000010001000111000001011111010110011010000
00000000000000000000000000100101101011111100000110000001111101001
00000000000000000000000001110100110101110010010010011001111010110
00000000000000000000000010101001110000110100110101100110001011011
00000000000000000000000101010001000100001110001011000110110001111
00000000000000000000001101011110100111011001001111100010110010001
00000000000000000000011100000001010110011010110100011010110001111
00000000000000000000100100010111111001010000101000011110000000101
00000000000000000001011101100000110000011100010001101010101000100
00000000000000000011011001101011000010000101101010011110010111010
00000000000000000101011011110011011010111110011100011101110011011
00000000000000001011101000001011101101011000000010101111101001101
00000000000000010001010111101010000111100001011101001001101010100
00000000000000111010100000111000010100001101000000000100111010100
00000000000001110111110101110000101100100110010111001111000111100
00000000000011000000001111000100011100100011111100011001001101100
00000000000100011011011111011011011010101101011010001111101000011
00000000001101010101111100001111110011011011001111110000100010100
00000000010011101000110001011011000111010110001001111111111011111
00000000111101011001001011100100100000111100101011101011000011100
00000001011000110011101011011100001010010000110001001101000100001
00000011101001001011011001011101110000111110010101011010001001111
00000111111000000011110100001100000100101001101100111101110111110
00001001111001001011010100011011101000010111101100100100100000110
00011011000111101010101000001111010110110000100011010101111101110
00111110011001110010111101111110110101100110011110110100000001000
01111011100000101000111110010011110110000100100010001001011010100
11010100000111000101100010011010100000101101100100110100001100111