Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 160. (Read 215479 times)

The key is how to write code to run the specified 0 and 1 digits on the gpu.

Also, I think that there is a high probability that the hexadecimal number of the private key for puzzle 66 starts with 3. That is, the highest 2 bits of the binary private key we can both set to 1, and we can specify the number of bits for 0s and 1s, and we can even search for less than just 2^63 private keys if we use bits with a probability of more than 40%! Of course, this is an extreme case, using too many coincidences.

If we continue to exclude combinations with negligible probability, such as 10 consecutive 0's or 1's, then the search space will be further reduced.

Simple combination for bits. Maybe someone can add some coding to convert 0s and 1s to hexadecimal, print in bat file, put it in bitcrack and run it.

Step 1

Let's say start scanning from 60 bits.

0s - 30 - 1s -30 = 50%
0s - 31 - 1s  29 = 51.67%
0s - 32 - 1s  28 = 53.4%
0s - 33 - 1s  27 = 55%
0s - 34 - 1s  26 = 56.67%
0s - 35 - 1s  25 = 58.34%
0s - 36 - 1s  24 = 60%

Then reverse 0s and 1s position in max 60% which is most likely where the key are.

Step 2
Convert Binary to Hexa

Step 3
Print in .CMD for continuous execution in Bitcrack.

Step 4
Run until it hits the key or else increase the percentages if it doesn't.

Make sense or any argument?

I am doing it already but doesn't have huge power like you guys. Maybe share it here and someone can crack it very soon here.

I guess that's what James idea trying to tell. Just start to scan from 50-50, 51-49, 52-48 and so on and it will save a lot of time and unnecessary scan from the beginning of useless less likely range.

I achieved the same result with 12 devices in a single machine

"
KeyHunt-Cuda v1.07

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Single Address
DEVICE       : GPU
CPU THREAD   : 0
GPU IDS      : 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
GPU GRIDSIZE : 16384x512, 16384x512, 16384x512, 16384x512, 16384x512, 16384x512, 16384x512, 16384x512, 16384x512, 16384x512, 16384x512, 16384x512
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  : 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
OUTPUT FILE  : Found.txt

Start Time   : Sat Aug 12 10:07:11 2023
Global start : 2E601111111111111 (66 bit)
Global end   : 40000000000000000 (67 bit)
Global range : 119FEEEEEEEEEEEEF (65 bit)

GPU          : GPU #4 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #6 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #9 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #2 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #7 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #1 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #0 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #3 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #8 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #10 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #11 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

GPU          : GPU #5 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(16384x512)

[00:04:38] [CPU+GPU: 71921.28 Mk/s] [GPU: 71921.28 Mk/s] [C: 0.000094 %] [R: 0] [T: 19,155,554,140,160 (45 bit)] [F: 0]
"

But the time is still not adding up... if you can do the calculations and also note the costs of renting the machines. you would end up resorting to random generation of at least the 1st 1 to 3 characters because scanning all that range from 20 to wherever you think the key would be doesn't cost pennies

but the 1s and 0s scanning can assure you you scanned all the ranges covering that specifically defined bit ranges without worries
and you can just keep doing it over and over again until you find the bit configuration for the specified puzzle you're searching for

vast.ai

where did you rent the cards ?

I am still waiting for an explanation for your defined term "optimized software"

The fastest I can achieve on a 14 * 4090 is below

GPU IDS      : 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
GPU GRIDSIZE : 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512, 2048x512
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  : 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
OUTPUT FILE  : Found.txt

Start Time   : Sat Aug 12 03:37:01 2023
Global start : 2CA60FFFFFFFFFFFF (66 bit)
Global end   : 40000000000000000 (67 bit)
Global range : 1359F000000000001 (65 bit)

GPU          : GPU #6 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #2 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #7 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #3 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #13 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #0 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #5 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #9 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #4 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #1 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #8 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #12 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #10 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

GPU          : GPU #11 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(2048x512)

[00:02:26] [CPU+GPU: 71119.07 Mk/s] [GPU: 71119.07 Mk/s] [C: 0.000047 %] [R: 0] [T: 10,526,964,842,496 (44 bit)] [F: 0]

So I want to understand your magic for the defined term optimized software

In my honest opinion, your idea is definitely have logic. Even if you can't find 66, you still have 67, 68, 69 unless all random hidden at top 70 or below 30.

Do you see any 80% or even 70% here? If he didn't see it, why is he so convince that James idea doesn't work? If you eliminate the less likely 80% above and 20% below, it is still kind of logical idea to eliminate those less likely key. Is that so difficult to understand? Nobody denying the key might be at above 80 or below 20, it's just less likely. That's what we call "Probability" in maths, not cluelessly brute forcing 100% of the range.

Exactly, it's just a logic to avoid brute force on all combinations. If it doesn't make sense, present your idea.

I'm reading the post and feel so funny about it.

I have no idea what's the point to argue about. One believe in power of random but another is discussing about math probability. You can even get 90% of 0 or 1 sometime but it's rare. James idea is just a type of probability to eliminate the less likely combination and doesn't guarantee it will find the key, as simple as that. Why is that so difficult to understand and try to bash people logical idea when they themselves can't find any. Is that so difficult to open the mind and listen to others?

Did you read the code?

Generate randomly without defining percentages.

I rented 4090s for 2 months. how do you think I lost the $23k?

what I need to know is what you meant by "optimized software"

Because I want to know your definition of searching the range wisely and not considering the speed and time and resources need and amount of investment or capital needed to complete the scan.

and I need to know your calculation for the keys/s and I know the best speed you can get on the 4090s is 5billion keys/s and if you use the keyhunt cuda you can use all the device in a machine to scan the range.

Please explain...

in this example I have entered 70% for imbalance of zero's and one's. Run the python program and enter 'inf' at the prompt and after a few seconds you will get a hit.


EDIT: here's another example using a spread of > 80% imbalance in less than 5 seconds after program start

and some additional ones even greater than > 85%

I also suggest to use "secrets" libary instead of "random" to generate true random numbers. The last two shown examples (>85% imbalance) shown here were using python's "secrets" library.
Is this enough to understand the meaning of randomness ?

Please, explain to me.

you have not (yet) understood

Check for yourself, generate a random key and tell us how many 1s and 0s it has. Do this at least 10 times and let us know.

absolutely, exactly my words

Puzzle #66 is not about pattern dudes

is all about logic and hardware power

If you have a bunch of 4090's out there and a optimized software to search it so you are in the game, If no you'll realize that is not simple as you think.

there's no pattern.