Total number of addresses that start with the same 11 characters = 2^66 / 58^(11 * log2(58))
First, calculate 58^(11 * log2(58)):
58^(11 * log2(58)) ≈ 58^42.614 ≈ 1.2107 × 10^74 (approximately)
Then, divide 2^66 by this result:
2^66 / 1.2107 × 10^74 ≈ 460708775.52
So, the approximate number of addresses that start with the same 11 characters from a key length of 2^66 bits is about 460,708,775.
Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 100. (Read 230098 times)
64 was solved before the 10x so the values of the fork coins were not as tempting as they are now.
Good to know that even after 12 minutes the fork coins were intact. So probably the situation is not that bad as we are anticipating
Then I just got the fork coins (only BCH, BSV, eCash, BTG, BCD and CDY) 
Good to know that even after 12 minutes the fork coins were intact. So probably the situation is not that bad as we are anticipating
I’m seeing so many variations of software throughout this thread and the other one. If I wanted to randomly let my pc waste electricity on weekends doing a random search for #66, what would be my best bet?
I have a 3070 and can switch to my Ubuntu partition if that’s better. I know my chances are probably like 0.001%, but I just want to feel like I’m joining the big boys on the hunt.
I have a 3070 and can switch to my Ubuntu partition if that’s better. I know my chances are probably like 0.001%, but I just want to feel like I’m joining the big boys on the hunt.
Then I just got the fork coins (only BCH, BSV, eCash, BTG, BCD and CDY)
Good to know that even after 12 minutes the fork coins were intact. So probably the situation is not that bad as we are anticipating
i assume any wallet program will just refuse to send a TX due to invalid signature.
Yes that is correct, even if you broadcast it manually the network nodes will not accept your transaction.
How was the Funds from Puzzle 64 transferred. There mist been a tug of war between the bots fighting each other during that time also. So how was it managed? Does someone know the story of that time. Same must have been for the Forks coin transfer of that puzzle as well. Another Tx another bot war ?
Hello there
I don't remember if there was a bot war for BTC in puzzle #64, but I got the privkey like 12 minutes after the pubkey was exposed (but only with CPU, I don't have GPU
) Then I just got the fork coins (only BCH, BSV, eCash, BTG, BCD and CDY)
Code:
● 12-char prefix
20d45a6a7625355df5e5fc41b358e6f8581991e2
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
20d45a6a7625355df5e5fc41b358e6f8581991e2
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
Did you realize that 0x8B8758F7C8AD0286 is near 1/3 of the 66 bit space?
Code:
>>> 2**65 // 0x8B8758F7C8AD0286
3
>>> 2**65 / 0x8B8758F7C8AD0286
3.6694959191703664
3
>>> 2**65 / 0x8B8758F7C8AD0286
3.6694959191703664
It just interesting
It seems to me that these calculations are very abstract, we are missing several steps for ripemd160. If this were really the case, then any addresses could be taken away without problems. I know you Alberto, we corresponded several times in tg. I am grateful to you in many ways, most likely thanks to you I started this activity. I have no goal of emptying other people’s wallets, but if one is found ownerless or from a puzzle, I will definitely send you a significant reward, rly. But, over time, I realized that this is more of a study, most likely this will never happen, maybe. Once again I apologize, I'm using a translator.
First, the leading 1, isn't part of the prefix, it is a gimme because all of these type addresses start with 1.
Someone correct me if I am wrong, but couldn't we just take range size / 58^number of leading prefixes (minus the starting "1")
If everything is uniformly spread out, over the range/curve (as the experts like to say, but it's not proven, but is a good "guesstimator" of sorts), an 11-char prefix (1 + 11 characters = total of 12 characters), in a 2^65 bit range, there should be around 1.4 of them. 2^65 / 58^11
2^65 / 58^11 = 1.4
2^65 / 58^10 = 85
2^65 / 58^9 = 4,967
2^65 / 58^8 = 288,088
and I guess you could apply a similar logic to H160s as well, but use 16^number of leading H160 prefixes, instead of 58^number of leading prefixes (minus the starting "1")
Anyone?
these last pages read like schizoposting.
anyway
what stops someone from sending invalid / badly signed TXs to the network so the bots are bogged down cracking the #66 with bad pubkeys? how does the network react in this case? does it just drop the bad transaction? or is it just not possible?
i could not find much on the subject of crafting invalid TXs, as i assume any wallet program will just refuse to send a TX due to invalid signature.
anyway
what stops someone from sending invalid / badly signed TXs to the network so the bots are bogged down cracking the #66 with bad pubkeys? how does the network react in this case? does it just drop the bad transaction? or is it just not possible?
i could not find much on the subject of crafting invalid TXs, as i assume any wallet program will just refuse to send a TX due to invalid signature.
Code:
● 12-char prefix
20d45a6a7625355df5e5fc41b358e6f8581991e2
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
20d45a6a7625355df5e5fc41b358e6f8581991e2
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
Did you realize that 0x8B8758F7C8AD0286 is near 1/3 of the 66 bit space?
Code:
>>> 2**65 // 0x8B8758F7C8AD0286
3
>>> 2**65 / 0x8B8758F7C8AD0286
3.6694959191703664
3
>>> 2**65 / 0x8B8758F7C8AD0286
3.6694959191703664
It just interesting
It seems to me that these calculations are very abstract, we are missing several steps for ripemd160. If this were really the case, then any addresses could be taken away without problems. I know you Alberto, we corresponded several times in tg. I am grateful to you in many ways, most likely thanks to you I started this activity. I have no goal of emptying other people’s wallets, but if one is found ownerless or from a puzzle, I will definitely send you a significant reward, rly. But, over time, I realized that this is more of a study, most likely this will never happen, maybe. Once again I apologize, I'm using a translator.
Code:
● 12-char prefix
20d45a6a7625355df5e5fc41b358e6f8581991e2
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
20d45a6a7625355df5e5fc41b358e6f8581991e2
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
Did you realize that 0x8B8758F7C8AD0286 is near 1/3 of the 66 bit space?
Code:
>>> 2**65 // 0x8B8758F7C8AD0286
3
>>> 2**65 / 0x8B8758F7C8AD0286
3.6694959191703664
3
>>> 2**65 / 0x8B8758F7C8AD0286
3.6694959191703664
It just interesting
Are you sure about this? Where did you get this information from? Will you share the source of this information?
Just simple addition, subtraction, multiplication and division math
Code:
● 7-char prefix
13zb1hQ111111111111111111111111111 => 20d45a6a4b704db750a2c2bd3f07159698d80d6e
13zb1hQzzzzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a9337b05029b466e310ca53586922d363
47c76298d911a425d1c33dc1d04ac5f5
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 47C76298D911A425D1C33DC1D04AC5F5 = 0x39106D151
(every 0x39106D151 will find 1 address 7-char prefix)
● 8-char prefix
13zb1hQb11111111111111111111111111 => 20d45a6a758414c1779b72697c32ea57a903e293
13zb1hQbzzzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76c0e5e769b1d1ee8d0e8eb7b1052c9c
13cd125f2165f8510dba46008014a09
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 13CD125F2165F8510DBA46008014A09 = 0xCEDB8B6C6A
(every 0xCEDB8B6C6A will find 1 address 8-char prefix)
● 9-char prefix
13zb1hQbW1111111111111111111111111 => 20d45a6a76227d5470a6a22c04a0bc87ad048798
13zb1hQbWzzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a7627f3b1c8afd8c8cb8a0a66056e7ba1
5765d5809369cc6e94dde5869f409
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 5765D5809369CC6E94DDE5869F409 = 0x2EDDBD96902D
(every 0x2EDDBD96902D will find 1 address 9-char prefix)
● 10-char prefix
13zb1hQbWV111111111111111111111111 => 20d45a6a76252067051503284157fc9abd37adf4
13zb1hQbWVzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a762538831cab3d7a68156376d939819c
181c17963a5226bd66dc1c01d3a8
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 181C17963A5226BD66DC1C01D3A8 = 0xA9E3CF41CAA3C
(every 0xA9E3CF41CAA3C will find 1 address 10-char prefix)
● 11-char prefix
13zb1hQbWVs11111111111111111111111 => 20d45a6a7625352fc9f79f5d6b915546d55c908e
13zb1hQbWVszzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a7625359a344e13210b21d70cd5d82eb0
6a6a5673c39f9081c6007b9e22
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 6A6A5673C39F9081C6007B9E22 = 0x267D9CF4E7E91B2
(every 0x267D9CF4E7E91B2 will find 1 address 11-char prefix)
● 12-char prefix
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
========= use My GPU - RTX 3090 ====== EXE: VanitySearch-1.15.4_bitcrack
>> Search 7-char prefix
VanitySearch.exe -t 0 -gpu -o 2D3C0C.txt --keyspace 2D3C0C00000000000:+39106D151FF 13zb1hQ
255 keys were supposed to be found, 267 keys were found
VanitySearch.exe -t 0 -gpu -o 2E2B98.txt --keyspace 2E2B9800000000000:+39106D151FF 13zb1hQ
255 keys were supposed to be found, 282 keys were found
VanitySearch.exe -t 0 -gpu -o 3A82BC.txt --keyspace 3A82BC00000000000:+39106D151FF 13zb1hQ
255 keys were supposed to be found, 289 keys were found
VanitySearch.exe -t 0 -gpu -o 354BAC.txt --keyspace 354BAC00000000000:+39106D15100 13zb1hQ
255 keys were supposed to be found, 256 keys were found
VanitySearch.exe -t 0 -gpu -o 222222.txt --keyspace 22222200000000000:+EFFFFFFFFFF 13zb1hQ
1076 keys were supposed to be found, 1012 keys were found
>> Search 8-char prefix
VanitySearch.exe -t 0 -gpu -o 2A82BC.txt --keyspace 2A82BC00000000000:+CEDB8B6C6AF 13zb1hQb
15 keys were supposed to be found, 10 keys were found
VanitySearch.exe -t 0 -gpu -o 2D13BA.txt --keyspace 2D13BA00000000000:+CEDB8B6C6AF 13zb1hQb
15 keys were supposed to be found, 10 keys were found
so I say.... ( puzzle 66 range 0x40000000000000000 - 0x20000000000000000 = 0x20000000000000000 )
13zb1hQbWV 10-char prefix match in ripemd160 hash will be little reference significance
0x20000000000000000 / 0xA9E3CF41CAA3C = 0x3038 ( 10000+ private key has 10 char prefix match compressed address )
13zb1hQbWVs 11-char prefix match
0x20000000000000000 / 0x267D9CF4E7E91B2 = 0xd4 ( 200~250 private key has 11 char prefix match compressed address )
13zb1hQbWVsc 12-char prefix match
0x20000000000000000 / 0x8B8758F7C8AD0286 = 0x3 ( 3~4 private key has 12 char prefix match compressed address )
13zb1hQ111111111111111111111111111 => 20d45a6a4b704db750a2c2bd3f07159698d80d6e
13zb1hQzzzzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a9337b05029b466e310ca53586922d363
47c76298d911a425d1c33dc1d04ac5f5
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 47C76298D911A425D1C33DC1D04AC5F5 = 0x39106D151
(every 0x39106D151 will find 1 address 7-char prefix)
● 8-char prefix
13zb1hQb11111111111111111111111111 => 20d45a6a758414c1779b72697c32ea57a903e293
13zb1hQbzzzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76c0e5e769b1d1ee8d0e8eb7b1052c9c
13cd125f2165f8510dba46008014a09
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 13CD125F2165F8510DBA46008014A09 = 0xCEDB8B6C6A
(every 0xCEDB8B6C6A will find 1 address 8-char prefix)
● 9-char prefix
13zb1hQbW1111111111111111111111111 => 20d45a6a76227d5470a6a22c04a0bc87ad048798
13zb1hQbWzzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a7627f3b1c8afd8c8cb8a0a66056e7ba1
5765d5809369cc6e94dde5869f409
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 5765D5809369CC6E94DDE5869F409 = 0x2EDDBD96902D
(every 0x2EDDBD96902D will find 1 address 9-char prefix)
● 10-char prefix
13zb1hQbWV111111111111111111111111 => 20d45a6a76252067051503284157fc9abd37adf4
13zb1hQbWVzzzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a762538831cab3d7a68156376d939819c
181c17963a5226bd66dc1c01d3a8
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 181C17963A5226BD66DC1C01D3A8 = 0xA9E3CF41CAA3C
(every 0xA9E3CF41CAA3C will find 1 address 10-char prefix)
● 11-char prefix
13zb1hQbWVs11111111111111111111111 => 20d45a6a7625352fc9f79f5d6b915546d55c908e
13zb1hQbWVszzzzzzzzzzzzzzzzzzzzzzz => 20d45a6a7625359a344e13210b21d70cd5d82eb0
6a6a5673c39f9081c6007b9e22
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 6A6A5673C39F9081C6007B9E22 = 0x267D9CF4E7E91B2
(every 0x267D9CF4E7E91B2 will find 1 address 11-char prefix)
● 12-char prefix
13zb1hQbWVsc1111111111111111111111 => 20d45a6a76253570014f1a30288bd88dc3ff6ffb
13zb1hQbWVsczzzzzzzzzzzzzzzzzzzzzz => 20d45a6a76253571d7012502fabee39e6bbaf2b4
1d5b20ad2d2330b10a7bb82b9
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF / 1D5B20AD2D2330B10A7BB82B9 = 0x8B8758F7C8AD0286
(every 0x8B8758F7C8AD0286 will find 1 address 12-char prefix)
========= use My GPU - RTX 3090 ====== EXE: VanitySearch-1.15.4_bitcrack
>> Search 7-char prefix
VanitySearch.exe -t 0 -gpu -o 2D3C0C.txt --keyspace 2D3C0C00000000000:+39106D151FF 13zb1hQ
255 keys were supposed to be found, 267 keys were found
VanitySearch.exe -t 0 -gpu -o 2E2B98.txt --keyspace 2E2B9800000000000:+39106D151FF 13zb1hQ
255 keys were supposed to be found, 282 keys were found
VanitySearch.exe -t 0 -gpu -o 3A82BC.txt --keyspace 3A82BC00000000000:+39106D151FF 13zb1hQ
255 keys were supposed to be found, 289 keys were found
VanitySearch.exe -t 0 -gpu -o 354BAC.txt --keyspace 354BAC00000000000:+39106D15100 13zb1hQ
255 keys were supposed to be found, 256 keys were found
VanitySearch.exe -t 0 -gpu -o 222222.txt --keyspace 22222200000000000:+EFFFFFFFFFF 13zb1hQ
1076 keys were supposed to be found, 1012 keys were found
>> Search 8-char prefix
VanitySearch.exe -t 0 -gpu -o 2A82BC.txt --keyspace 2A82BC00000000000:+CEDB8B6C6AF 13zb1hQb
15 keys were supposed to be found, 10 keys were found
VanitySearch.exe -t 0 -gpu -o 2D13BA.txt --keyspace 2D13BA00000000000:+CEDB8B6C6AF 13zb1hQb
15 keys were supposed to be found, 10 keys were found
so I say.... ( puzzle 66 range 0x40000000000000000 - 0x20000000000000000 = 0x20000000000000000 )
13zb1hQbWV 10-char prefix match in ripemd160 hash will be little reference significance
0x20000000000000000 / 0xA9E3CF41CAA3C = 0x3038 ( 10000+ private key has 10 char prefix match compressed address )
13zb1hQbWVs 11-char prefix match
0x20000000000000000 / 0x267D9CF4E7E91B2 = 0xd4 ( 200~250 private key has 11 char prefix match compressed address )
13zb1hQbWVsc 12-char prefix match
0x20000000000000000 / 0x8B8758F7C8AD0286 = 0x3 ( 3~4 private key has 12 char prefix match compressed address )
I have two 11-char prefix match address and private in 66 range
13zb1hQbWVsoqtKv6BRRpKZ81caz7KWea5
13zb1hQbWVsSAaNvpKfmc43NsuAj33LyRM
How was the Funds from Puzzle 64 transferred. There mist been a tug of war between the bots fighting each other during that time also. So how was it managed? Does someone know the story of that time. Same must have been for the Forks coin transfer of that puzzle as well. Another Tx another bot war ?
Well that is a good question, but unless someone recorded the mempool TX related to that address at that time there is no way to know for sure because after some time all those TX that didn't win the "bid" fight are promptly discarded from most of the servers that show TX details online.
One example of that is what i write in Is FullRBF allowing double spend? where i show some TX tha are related to one of my addresses and those TX no longer exists because they were FullRBF with new TX.
How was the Funds from Puzzle 64 transferred. There mist been a tug of war between the bots fighting each other during that time also. So how was it managed? Does someone know the story of that time. Same must have been for the Forks coin transfer of that puzzle as well. Another Tx another bot war ?
There's simply no feasible way to withdraw the funds on lower end puzzles like #66. It will be snatched up by bots. Not maybe, but it's 100% guaranteed. There will be hundreds of withdrawal transactions with varying fees all battling each other. You will simply be left in the dust.
It's a fundamental flaw in this puzzle that was originally aimed to bring the community together and try to solve the puzzle. The puzzle creator did not think much about the puzzle, and this is proof of it.
The only way the original solver will get the funds of puzzle #66 is if they can prove to be in possession of the private keys directly to the puzzle creator. The puzzle creator then withdraws the funds at a 6BTC fee (they can afford it) to your address.
It's a fundamental flaw in this puzzle that was originally aimed to bring the community together and try to solve the puzzle. The puzzle creator did not think much about the puzzle, and this is proof of it.
The only way the original solver will get the funds of puzzle #66 is if they can prove to be in possession of the private keys directly to the puzzle creator. The puzzle creator then withdraws the funds at a 6BTC fee (they can afford it) to your address.
The goal of the puzzles is to demonstrate the strength of bitcoin and so far it has more than proven that.
I don't think the creator cares about the method by which the private key is obtained, whether it's years of brute force, whether it's discovering a pattern or through social engineering, the owner of the private key is the owner of the coins. If there is more than one transaction with the same private key, the protocol designed to resolve double spending will be applied.
End of story
Sure tx you had made is different subject.
There's simply no feasible way to withdraw the funds on lower end puzzles like #66. It will be snatched up by bots. Not maybe, but it's 100% guaranteed. There will be hundreds of withdrawal transactions with varying fees all battling each other. You will simply be left in the dust.
It's a fundamental flaw in this puzzle that was originally aimed to bring the community together and try to solve the puzzle. The puzzle creator did not think much about the puzzle, and this is proof of it.
The only way the original solver will get the funds of puzzle #66 is if they can prove to be in possession of the private keys directly to the puzzle creator. The puzzle creator then withdraws the funds at a 6BTC fee (they can afford it) to your address.
It's a fundamental flaw in this puzzle that was originally aimed to bring the community together and try to solve the puzzle. The puzzle creator did not think much about the puzzle, and this is proof of it.
The only way the original solver will get the funds of puzzle #66 is if they can prove to be in possession of the private keys directly to the puzzle creator. The puzzle creator then withdraws the funds at a 6BTC fee (they can afford it) to your address.
The goal of the puzzles is to demonstrate the strength of bitcoin and so far it has more than proven that.
I don't think the creator cares about the method by which the private key is obtained, whether it's years of brute force, whether it's discovering a pattern or through social engineering, the owner of the private key is the owner of the coins. If there is more than one transaction with the same private key, the protocol designed to resolve double spending will be applied.
End of story
There's simply no feasible way to withdraw the funds on lower end puzzles like #66. It will be snatched up by bots. Not maybe, but it's 100% guaranteed. There will be hundreds of withdrawal transactions with varying fees all battling each other. You will simply be left in the dust.
It's a fundamental flaw in this puzzle that was originally aimed to bring the community together and try to solve the puzzle. The puzzle creator did not think much about the puzzle, and this is proof of it.
The only way the original solver will get the funds of puzzle #66 is if they can prove to be in possession of the private keys directly to the puzzle creator. The puzzle creator then withdraws the funds at a 6BTC fee (they can afford it) to your address.
It's a fundamental flaw in this puzzle that was originally aimed to bring the community together and try to solve the puzzle. The puzzle creator did not think much about the puzzle, and this is proof of it.
The only way the original solver will get the funds of puzzle #66 is if they can prove to be in possession of the private keys directly to the puzzle creator. The puzzle creator then withdraws the funds at a 6BTC fee (they can afford it) to your address.
WTF? You are showing a pattern in the ASCII values of the characters 0 to 9.
Sure there is a pattern in there, since they are consecutive values starting from '0' to '9'.
So your pattern is just the ASCII offset for character '0', which is 0x30, e.g. '0011 0000' in binary up to '0011 1001'.
Hence your "pattern".
Sure there is a pattern in there, since they are consecutive values starting from '0' to '9'.
So your pattern is just the ASCII offset for character '0', which is 0x30, e.g. '0011 0000' in binary up to '0011 1001'.
Hence your "pattern".
========================================================================================
I spent over a year searching for #66 and even made a Nvidia Kernel to shuffle using nvcc and OpenSSL-Win64.
I have abandoned the search due to the withdrawal front runners and have been selling all my RTX GPUs anyway.
Let me show you something, if focus only on puzzles divisible by 6:
#Puzzle privkeys in binary
110001 #6
101001 111011 #12
110000 100000 001101 #18
110111 000010 101000 000100 #24
111101 100101 001100 110101 100100 #30
100111 011110 100000 100000 101001 111100 #36
101010 001000 100001 110001 011000 110110 001111 #42
101011 011110 011011 010111 110011 100011 101110 011011 #48
100011 011011 111011 011011 010101 101011 010001 111101 000011 #54
111111 000000 011110 100001 100000 100101 001101 100111 101110 111110 #60
patrn1 patrn2 patrn3 patrn4 patrn5 patrn6 patrn7 patrn8 patrn9 patrn10 patrn11 #66
101100 111000 000000 101110 110010 000100 110110 101001 000100 010111 000111 000111 101000 010110 111111 #90
the above puzzle solutions could all be derived shuffling the below pool of patterns:
"101001", "111011", "110111", "000010", "101000", "000100", "011110", "111100", "101011", "011011", "010111",
"110011", "100011", "111111", "000000", "100001", "100000", "100101", "001101", "100111", "101110", "111110",
"110101", "110001", "111101", "001100", "100100", "101100", "111000", "110010", "110110", "000111", "010110",
"110000", "101010", "001000", "011000", "001111", "010101", "010001", "000011"
however some patterns are missing, below is the full pool of 64 patterns,
we can be confident that #66 can be solved by stringing the correct 11 patterns below together:
also understand that #72 can be solved by stringing the correct 12 patterns below together and #78 can be solved with
the correct 13 patterns etc.
"000001", "000011", "000111", "001000", "010101", "110001", "100110", "111000", "111010", "100000", "100100",
"101001", "111011", "101000", "110000", "001100", "011110", "010011", "101110", "110010", "001101", "101011",
"101101", "000000", "111101", "110111", "010010", "100101", "100111", "110011", "110101", "101010", "001001",
"100010", "101111", "111110", "001010", "100011", "010111", "011000", "011001", "011010", "011011", "011100",
"111111", "000010", "000101", "010001", "010100", "010110", "010000", "011101", "001011", "101100", "011111",
"000100", "110100", "110110", "111001", "001110", "000110", "111100", "001111", "100001"
Example only:
patrn1 patrn2 patrn3 patrn4 patrn5 patrn6 patrn7 patrn8 patrn9 patrn10 patrn11 13zb1hQbWvsAVRom8TVv262i3JryAo2LqU
110100 101011 001110 010001 111001 010110 110000 110010 111110 001100 100010 (33zeros 33ones) =20d45a6a76278fff811c3fb04e3e9df1fd775808 hash160 test target
solution = 0000000000000000000000000000000000000000000000034ACE4795B0CBE322
patrn1 can only choose between:
"110100"
patrn2 can only choose between:
"101011"
patrn3 can only choose between:
"XXXXXX", "001110", "XXXXXX", "XXXXXX", "XXXXXX"
patrn4 can only choose between:
"010001", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX"
patrn5 can only choose between:
"XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "111001", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX",
"XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX"
patrn6 to patrn11 can only choose between:
"000001", "000011", "000111", "001000", "010101", "110001", "100110", "111000", "111010", "100000", "100100",
"101001", "111011", "101000", "110000", "001100", "011110", "010011", "101110", "110010", "001101", "101011",
"101101", "000000", "111101", "110111", "010010", "100101", "100111", "110011", "110101", "101010", "001001",
"100010", "101111", "111110", "001010", "100011", "010111", "011000", "011001", "011010", "011011", "011100",
"111111", "000010", "000101", "010001", "010100", "010110", "010000", "011101", "001011", "101100", "011111",
"000100", "110100", "110110", "111001", "001110", "000110", "111100", "001111", "100001"
---------------------------------------------
The actual #66 is probably something like this:
patrn1:
"110100", "110111", "110101", "110011", "110000", "110010", "111000"
patrn2
"101001", "101000", "101110", "101011", "101101", "101010", "101111", "101100", "001110", "110011", "011111",
"000011", "010001", "000000", "000001", "000110", "000101", "111010"
patrn3
"001110", "100110", "010001", "111110", "110011", "011001", "101001", "101110", "010011", "110110", "111001",
"110111", "111111"
patrn4
"110111", "001110", "100110", "011001", "100111", "101011", "111110", "010010", "011000", "000011", "010001",
"110101", "000001", "101001", "001001", "001100", "110000", "000110", "101110", "010111", "101010", "010100",
"011101", "000100", "111010", "000101", "001111", "101101", "011011", "111011", "000000", "111111", "011100"
patrn5 to patrn11
"000001", "000011", "000111", "001000", "010101", "110001", "100110", "111000", "111010", "100000", "100100",
"101001", "111011", "101000", "110000", "001100", "011110", "010011", "101110", "110010", "001101", "101011",
"101101", "000000", "111101", "110111", "010010", "100101", "100111", "110011", "110101", "101010", "001001",
"100010", "101111", "111110", "001010", "100011", "010111", "011000", "011001", "011010", "011011", "011100",
"111111", "000010", "000101", "010001", "010100", "010110", "010000", "011101", "001011", "101100", "011111",
"000100", "110100", "110110", "111001", "001110", "000110", "111100", "001111", "100001"
I'll share this as maybe it can help someone:
patrn1 patrn2 patrn3 patrn4 patrn5 patrn6 patrn7 patrn8 patrn9 patrn10 patrn11 13zb1hQbWVs c2S7ZTZnP2G4undNNpdh5so KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q
110100 101011 001110 010001 111001 010110 110000 110010 111110 001100 100010 33zeros 33ones 13zb1hQbWvs AVRom8TVv262i3JryAo2LqU 34ACE4795B0CBE322 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZwtAjExHC7qVuCaDqDK
110111 001110 100110 011001 100111 101010 010100 010111 000110 001001 011101 31zeros 35ones 13ZB1HqbWVS FCCWUSWSB43W4vzgHdLhRMS 373A6667A945C625D KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1HV4GqwfMNz9Nqecu2
110101 011111 010001 001001 010011 001000 011111 100110 000111 000010 011110 33zeros 33ones 13zB1HqBWvs kyLE2wzSqtU8pCr4Z28PXQn 357D125321F98709E KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZxy2Pr7XrGPpA5QuczP
110111 101011 111110 010010 011000 101011 000011 110101 111010 000100 100111 29zeros 37ones* 13Zb1hQBwVS zcX7L3KsxLMykonkpXui5r7 37AFE498AC3D7A127 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1txcTqpmeSt3KytEyM
110111 000011 010001 110101 111110 111011 101010 011011 101101 001111 000101 26zeros 40ones 13zb1HqBwvs JPswzHYKoCEvYZV39Tzp2U4 370D1D7EEEA6ED3C5 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa13p2GHVdjaxUyF8LEw
110010 111010 110110 110101 011111 111100 000000 101011 111111 000011 111000 27zeros 39ones 13zb1HqBwvS yw8Ys9WxCg8fFVttcJVArXf 32EB6D5FF00AFF0F8 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZuYTd3zEiCPVEvjbGDu
110011 010001 110011 101101 101101 101001 001000 111100 011100 110001 100100 32zeros 34ones 13zb1HqbWvS BE8YL37m85gYB8JXduPzP9Y 33473B6DA48F1CC64 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZv2BKmQjbBkqFByafaA
110011 000000 011001 011000 101000 010010 001011 001010 011101 101101 001101 37zeros 29ones 13Zb1HQBWVs 2Z7cwTTHnbt4UC8XmZRuoUP 3301962848B29DB4D KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZuf9gNnoF21yZ7vdxpo
110111 000001 101001 001001 001100 011100 100110 010111 111111 000000 101110 33zeros 33ones 13Zb1HqbWVs Rj3qjfV4azxNegobGLE2Wm8 3706924C7265FF02E KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa11qRkheWzW1nYQiXmZ
110000 000110 101110 010111 101010 001110 001001 000110 001100 100010 110011 36zeros 30ones* 13Zb1HQbwvs F9H25ugdHKQK2N6NWsv3LJM 301AE5EA38918C8B3 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZqnubqDyHhuPVYg8B6H
110011 000101 010011 101100 001000 111011 111011 100011 111110 000111 010000 31zeros 35ones 13ZB1hqBWvs LGFeQMpAeg9Q3rzM9ok8MGx 33153B08EFB8FE1D0 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZum5gwhZVimMiSoVxii
Cheers
======================================================
I spent over a year searching for #66 and even made a Nvidia Kernel to shuffle using nvcc and OpenSSL-Win64.
I have abandoned the search due to the withdrawal front runners and have been selling all my RTX GPUs anyway.
Let me show you something, if focus only on puzzles divisible by 6:
#Puzzle privkeys in binary
110001 #6
101001 111011 #12
110000 100000 001101 #18
110111 000010 101000 000100 #24
111101 100101 001100 110101 100100 #30
100111 011110 100000 100000 101001 111100 #36
101010 001000 100001 110001 011000 110110 001111 #42
101011 011110 011011 010111 110011 100011 101110 011011 #48
100011 011011 111011 011011 010101 101011 010001 111101 000011 #54
111111 000000 011110 100001 100000 100101 001101 100111 101110 111110 #60
patrn1 patrn2 patrn3 patrn4 patrn5 patrn6 patrn7 patrn8 patrn9 patrn10 patrn11 #66
101100 111000 000000 101110 110010 000100 110110 101001 000100 010111 000111 000111 101000 010110 111111 #90
the above puzzle solutions could all be derived shuffling the below pool of patterns:
"101001", "111011", "110111", "000010", "101000", "000100", "011110", "111100", "101011", "011011", "010111",
"110011", "100011", "111111", "000000", "100001", "100000", "100101", "001101", "100111", "101110", "111110",
"110101", "110001", "111101", "001100", "100100", "101100", "111000", "110010", "110110", "000111", "010110",
"110000", "101010", "001000", "011000", "001111", "010101", "010001", "000011"
however some patterns are missing, below is the full pool of 64 patterns,
we can be confident that #66 can be solved by stringing the correct 11 patterns below together:
also understand that #72 can be solved by stringing the correct 12 patterns below together and #78 can be solved with
the correct 13 patterns etc.
"000001", "000011", "000111", "001000", "010101", "110001", "100110", "111000", "111010", "100000", "100100",
"101001", "111011", "101000", "110000", "001100", "011110", "010011", "101110", "110010", "001101", "101011",
"101101", "000000", "111101", "110111", "010010", "100101", "100111", "110011", "110101", "101010", "001001",
"100010", "101111", "111110", "001010", "100011", "010111", "011000", "011001", "011010", "011011", "011100",
"111111", "000010", "000101", "010001", "010100", "010110", "010000", "011101", "001011", "101100", "011111",
"000100", "110100", "110110", "111001", "001110", "000110", "111100", "001111", "100001"
Example only:
patrn1 patrn2 patrn3 patrn4 patrn5 patrn6 patrn7 patrn8 patrn9 patrn10 patrn11 13zb1hQbWvsAVRom8TVv262i3JryAo2LqU
110100 101011 001110 010001 111001 010110 110000 110010 111110 001100 100010 (33zeros 33ones) =20d45a6a76278fff811c3fb04e3e9df1fd775808 hash160 test target
solution = 0000000000000000000000000000000000000000000000034ACE4795B0CBE322
patrn1 can only choose between:
"110100"
patrn2 can only choose between:
"101011"
patrn3 can only choose between:
"XXXXXX", "001110", "XXXXXX", "XXXXXX", "XXXXXX"
patrn4 can only choose between:
"010001", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX"
patrn5 can only choose between:
"XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "111001", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX",
"XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX", "XXXXXX"
patrn6 to patrn11 can only choose between:
"000001", "000011", "000111", "001000", "010101", "110001", "100110", "111000", "111010", "100000", "100100",
"101001", "111011", "101000", "110000", "001100", "011110", "010011", "101110", "110010", "001101", "101011",
"101101", "000000", "111101", "110111", "010010", "100101", "100111", "110011", "110101", "101010", "001001",
"100010", "101111", "111110", "001010", "100011", "010111", "011000", "011001", "011010", "011011", "011100",
"111111", "000010", "000101", "010001", "010100", "010110", "010000", "011101", "001011", "101100", "011111",
"000100", "110100", "110110", "111001", "001110", "000110", "111100", "001111", "100001"
---------------------------------------------
The actual #66 is probably something like this:
patrn1:
"110100", "110111", "110101", "110011", "110000", "110010", "111000"
patrn2
"101001", "101000", "101110", "101011", "101101", "101010", "101111", "101100", "001110", "110011", "011111",
"000011", "010001", "000000", "000001", "000110", "000101", "111010"
patrn3
"001110", "100110", "010001", "111110", "110011", "011001", "101001", "101110", "010011", "110110", "111001",
"110111", "111111"
patrn4
"110111", "001110", "100110", "011001", "100111", "101011", "111110", "010010", "011000", "000011", "010001",
"110101", "000001", "101001", "001001", "001100", "110000", "000110", "101110", "010111", "101010", "010100",
"011101", "000100", "111010", "000101", "001111", "101101", "011011", "111011", "000000", "111111", "011100"
patrn5 to patrn11
"000001", "000011", "000111", "001000", "010101", "110001", "100110", "111000", "111010", "100000", "100100",
"101001", "111011", "101000", "110000", "001100", "011110", "010011", "101110", "110010", "001101", "101011",
"101101", "000000", "111101", "110111", "010010", "100101", "100111", "110011", "110101", "101010", "001001",
"100010", "101111", "111110", "001010", "100011", "010111", "011000", "011001", "011010", "011011", "011100",
"111111", "000010", "000101", "010001", "010100", "010110", "010000", "011101", "001011", "101100", "011111",
"000100", "110100", "110110", "111001", "001110", "000110", "111100", "001111", "100001"
I'll share this as maybe it can help someone:
patrn1 patrn2 patrn3 patrn4 patrn5 patrn6 patrn7 patrn8 patrn9 patrn10 patrn11 13zb1hQbWVs c2S7ZTZnP2G4undNNpdh5so KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q
110100 101011 001110 010001 111001 010110 110000 110010 111110 001100 100010 33zeros 33ones 13zb1hQbWvs AVRom8TVv262i3JryAo2LqU 34ACE4795B0CBE322 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZwtAjExHC7qVuCaDqDK
110111 001110 100110 011001 100111 101010 010100 010111 000110 001001 011101 31zeros 35ones 13ZB1HqbWVS FCCWUSWSB43W4vzgHdLhRMS 373A6667A945C625D KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1HV4GqwfMNz9Nqecu2
110101 011111 010001 001001 010011 001000 011111 100110 000111 000010 011110 33zeros 33ones 13zB1HqBWvs kyLE2wzSqtU8pCr4Z28PXQn 357D125321F98709E KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZxy2Pr7XrGPpA5QuczP
110111 101011 111110 010010 011000 101011 000011 110101 111010 000100 100111 29zeros 37ones* 13Zb1hQBwVS zcX7L3KsxLMykonkpXui5r7 37AFE498AC3D7A127 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1txcTqpmeSt3KytEyM
110111 000011 010001 110101 111110 111011 101010 011011 101101 001111 000101 26zeros 40ones 13zb1HqBwvs JPswzHYKoCEvYZV39Tzp2U4 370D1D7EEEA6ED3C5 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa13p2GHVdjaxUyF8LEw
110010 111010 110110 110101 011111 111100 000000 101011 111111 000011 111000 27zeros 39ones 13zb1HqBwvS yw8Ys9WxCg8fFVttcJVArXf 32EB6D5FF00AFF0F8 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZuYTd3zEiCPVEvjbGDu
110011 010001 110011 101101 101101 101001 001000 111100 011100 110001 100100 32zeros 34ones 13zb1HqbWvS BE8YL37m85gYB8JXduPzP9Y 33473B6DA48F1CC64 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZv2BKmQjbBkqFByafaA
110011 000000 011001 011000 101000 010010 001011 001010 011101 101101 001101 37zeros 29ones 13Zb1HQBWVs 2Z7cwTTHnbt4UC8XmZRuoUP 3301962848B29DB4D KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZuf9gNnoF21yZ7vdxpo
110111 000001 101001 001001 001100 011100 100110 010111 111111 000000 101110 33zeros 33ones 13Zb1HqbWVs Rj3qjfV4azxNegobGLE2Wm8 3706924C7265FF02E KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa11qRkheWzW1nYQiXmZ
110000 000110 101110 010111 101010 001110 001001 000110 001100 100010 110011 36zeros 30ones* 13Zb1HQbwvs F9H25ugdHKQK2N6NWsv3LJM 301AE5EA38918C8B3 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZqnubqDyHhuPVYg8B6H
110011 000101 010011 101100 001000 111011 111011 100011 111110 000111 010000 31zeros 35ones 13ZB1hqBWvs LGFeQMpAeg9Q3rzM9ok8MGx 33153B08EFB8FE1D0 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZum5gwhZVimMiSoVxii
Cheers
======================================================
Send me PM pls. I can share 1 WVs if u share too. This of course doesn't make sense lol
Already sent you a private message , exchange 1 private key of 13zb1hQbWVs********* ( 0x20000000000000000 ~ 0x40000000000000000 )
The address is the private key of 13zb1hQbWVsSAaNvpKfmc43NsuAj33LyRM
This is for reference only, I will give up on searching from ranges around 11 char #66
Jump to: