[ARCHIVE] Bitcoin challenge discusion

[mrxtraf]

Cool!


I made a php script to generate these results



b848af95c31c7000 - 33
b479223fc70f9800 - 33
a51b778c1dfa9800 - 35
cb5da3803496e000 - 31
8565165d73359800 - 31
ad9aa9f1d9c8d800 - 32
eae9d06a0dda3800 - 31
fc8699e06b942800 - 33
a87bcad3cafd3000 - 35
8b1d03767b88a800 - 30
fee40c87ff868000 - 31
9220d796b49bf000 - 32
9cc62606451f3000 - 29
b434b1ce9248f800 - 30
df1f7444b94e1000 - 34
fce5d65a4292f800 - 33
b642d85cb2fc2000 - 32
ac41754b49cb7800 - 32
bab931fe60882800 - 29
b7460cbcef883800 - 33
974fec034a650000 - 33
c6e327436c5e2000 - 31
e296a30a15cb6000 - 32
e9a6e8e8e14aa800 - 35
e369e4cce3a34800 - 35
886a4d6f9e9da000 - 35
da38c5fbc6962000 - 34
935afac54cff3000 - 35
f888618436e3f000 - 31
f3765981ce08f000 - 35
f6e9901d68c6a000 - 33
acb846ffc364a800 - 34
d0c4871bc5f30800 - 31
808784ef692fa000 - 33
8e4f264b62afe800 - 35
c7c80bdf8662d800 - 35
f9e2c298a10a7800 - 31
b97fee8bcc381000 - 35
ecb66958f8647800 - 34
ab4c5897a1462800 - 30
8e7c489527c5b000 - 33
88bc8a4e511b9000 - 29
81b2dc63cd700000 - 29
dfad627e5a748000 - 33
ddac4c0b7c2a5800 - 33
bc11ee44dc75a000 - 31
f46cc5146107a800 - 32
9f6aceb734112000 - 34
cf729a5e068cb800 - 33
ae12f3f0b5c44800 - 34
dd04d9ccba00a800 - 29
e9c3b64ad352c000 - 34
ba1c7dbb13ab0800 - 34
c4b25d1e22e95000 - 32
b5a90a950dfd7800 - 33
ea260d7b0d521800 - 34
ecbb5827bd50a800 - 33
89de30a6ba1d4000 - 34
9bed13cbcb5c7000 - 35
dacfbbe538855800 - 35
fcd919c8fe255800 - 33
a17db402f748d800 - 33


code:

Code:

<?php
for($i=0;$i<100;$i++){
$bytes = 1 . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) . rand(0,1) ;


if(substr_count($bytes, '1') >= 29 && substr_count($bytes, '1') <= 35){
echo dechex(bindec($bytes)) . " - " . substr_count($bytes, '1') .'<br>';
}
}



?>

Nice script. But very simple, and slow.
Try on the basis of it to do incremental search starting from scratch! 100000000 .....

[1714768977]

1714768977

[1714768977]

1714768977

[MrFreeDragon]

Why is 45% -55%? If you take the data from the table excluding the first ten keys. Then we get a minimum value of 31% and a maximum of 68%.

45-50% is my guess based on the analysis and statistic logics. The first keys are not representative due to higher dispersion, so it is better to exclude not 10 first keys but at least 15, of even 20.

The idea is that "the higher the bit --> the tighter dispersion". As the probability of 1 or 0 bit is always 50% for every bit, so the total quantity of "1"s (or "0"s) will tend to 50% in higher bits keys.

That is, the search difference will be in the range of 31% -69% of the bits set to 1 or 0.

Such "wide" range could be applicable only for low bit keys. But for higher bit keys the dispersion will be narrow.
Try to flip a coin 100 times --> more likely you will have at least 45 Heads but not more than 55 (the same for tails).
You can not take the results from the "10-15 times" coin flips and apply them to the random number where you flip the coin 100 times. No, the "heads" probability (number of "1"s) will tend to 50% while you increase the quantity of flips (bit value of the key).

Of course, everthing is possible, even the key with only 10% of "1"s, BUT morelikely for high bit keys the quantity of "1"s is within 45-55% range. Moreover, for keys higher than 140-150bit, i beleive that the quantity of "1"s is 46-54% or even 47-53%.

PS. All these calcualtions could be proved mathematically with the certain level of assurance.

[Mandoy]

I have been trying to solve the puzzle but every time I tried I got an headache. I dont know where to start and I keep on researching until I end up with nothing. I even ask some of my friends who are good with this things but I cannot understand fully their explanation. I guess I will stop doing the challenge and will focus on the signature campaign. Well good luck to you guys in solving the puzzle its hopeless for me.

[bounty0z]

I have been trying to solve the puzzle but every time I tried I got an headache. I dont know where to start and I keep on researching until I end up with nothing. I even ask some of my friends who are good with this things but I cannot understand fully their explanation. I guess I will stop doing the challenge and will focus on the signature campaign. Well good luck to you guys in solving the puzzle its hopeless for me.

No just don't give up , we all know that is too hard, and all end up got an headache because its look like impossible, but if you have material so you can do it, I tried all this week from morning to night to find it but still nothing, because even minimze rang of search its still will take months to finish. I don't have good material but keep trying  ;
So good luck to everyone

[MrFreeDragon]

I will stop doing the challenge and will focus on the signature campaign. Well good luck to you guys in solving the puzzle its hopeless for me.

I don't have good material but keep trying  ;
So good luck to everyone

Hmm.. your both messages look like you are asking to increase the bounties again  For example from 0.64BTC up to 6.4BTC for wallet #64 and so on

[mrxtraf]

I have been trying to solve the puzzle but every time I tried I got an headache. I dont know where to start and I keep on researching until I end up with nothing. I even ask some of my friends who are good with this things but I cannot understand fully their explanation. I guess I will stop doing the challenge and will focus on the signature campaign. Well good luck to you guys in solving the puzzle its hopeless for me.

Just a every day.
https://www.youtube.com/watch?v=im2VlRprLVc

[pilot1970]

That is a very complex problem and addressed to experts in programming, I will be watching to see who sends the solution.

[conglyvaness]

Thanks for the info regarding the "challenge". I was not sure about the right form :-) As to the percentage ranges - I took them personally into account, but I do not plan to base them in my actions, because they would be shots on the basis of statistics, and again complicating my life. It is not known whether now there will be three subsequent addresses had their key in the range of 90-100% .... and maybe even the rest of the keys below 50% :-)

[iparktur]

I have been trying to solve the puzzle but every time I tried I got an headache. I dont know where to start and I keep on researching until I end up with nothing. I even ask some of my friends who are good with this things but I cannot understand fully their explanation. I guess I will stop doing the challenge and will focus on the signature campaign. Well good luck to you guys in solving the puzzle its hopeless for me.

Just a every day.
https://www.youtube.com/watch?v=im2VlRprLVc

It is not clear what you are doing there and what result you get?
Write me in PM.

[MrFreeDragon]

Just a every day.
https://www.youtube.com/watch?v=im2VlRprLVc

Funny game ) I found there a square 16x16 visualizing the key in BIN format. Last month I also created a tool to generate a bitcoin address in coin mode and visualize the existing keys (https://btckeygen.com/). I made the visualizations of all known puzzle keys to find the pstterns, but could not. I made a conclusion that the keys were random   With no patterns  

[bounty0z]

Just a every day.
https://www.youtube.com/watch?v=im2VlRprLVc

Funny game ) I found there a square 16x16 visualizing the key in BIN format. Last month I also created a tool to generate a bitcoin address in coin mode and visualize the existing keys (https://btckeygen.com/). I made the visualizations of all known puzzle keys to find the pstterns, but could not. I made a conclusion that the keys were random   With no patterns  

How many private key can be generated per second using this tool ? I am not sure but when I watch th video its look like take more time + don't forget that using bitcrack and gpu can create more than 100Mkey if you have good resources, so this game should take lot and lot of time than bitcrack.
and at all its just chance, you can get it fast if you have chance

[mrxtraf]

Just a every day.
https://www.youtube.com/watch?v=im2VlRprLVc

Funny game ) I found there a square 16x16 visualizing the key in BIN format. Last month I also created a tool to generate a bitcoin address in coin mode and visualize the existing keys (https://btckeygen.com/). I made the visualizations of all known puzzle keys to find the pstterns, but could not. I made a conclusion that the keys were random   With no patterns  

How many private key can be generated per second using this tool ? I am not sure but when I watch th video its look like take more time + don't forget that using bitcrack and gpu can create more than 100Mkey if you have good resources, so this game should take lot and lot of time than bitcrack.
and at all its just chance, you can get it fast if you have chance

Yes, the visualizer is designed for chance. The speed is small enough, it’s just sometimes not interesting to watch. But there are not just random numbers, there are also some checks that were discussed in this or a neighboring branch. For example, a repeating sequence of identical bits cannot exceed 8, this is a type, for example. Another algorithm changes only one random bit from the last option.

[MrFreeDragon]

But there are not just random numbers, there are also some checks that were discussed in this or a neighboring branch. For example, a repeating sequence of identical bits cannot exceed 8, this is a type, for example. Another algorithm changes only one random bit from the last option.

So you just confirm that the key is random! Your example like "that the same bit could not repeat more than 8 times" just prove that the key is random.

How do you think the real random works? The random number is not selected within the eide range, no. The random is applied to every bit. So, the random entropy was used to create each bit in random way, which is absolutely 50%/50% for every bit.
That's why there is no pattern. That's why it is so hard to guess and find any connections. When you apply 50% probability for every single bit, so you do not guess and imagine how is the whole key will look, it is really not important.

I beleive that all the keys for this puzzle transactions were generated randomly on the lowest level - on bit level.

[bounty0z]

But there are not just random numbers, there are also some checks that were discussed in this or a neighboring branch. For example, a repeating sequence of identical bits cannot exceed 8, this is a type, for example. Another algorithm changes only one random bit from the last option.

So you just confirm that the key is random! Your example like "that the same bit could not repeat more than 8 times" just prove that the key is random.

Please I Have Question to you MrFreeDragon ,Why the one who code kangaroo use CPU ,why didn't use GPU to accelerate the code and get the solution faster , I use the same code of Kangaroo and I have only 10k H/s but other membres result is 100k H/s !! thats mean my cpu is low, but why not use cuda gpu ? and thanks

[mrxtraf]

I do not argue that the keys from the puzzle were obtained randomly. What was this generator, bitwise, ekdska, super random, etc. irrelevant.
But here we go into the theory of probability. For example, if you get a random number from 1 to 100, then theoretically one kind of number, for example 3, can fall 10 times in a row. But it is theoretically. If in practice this happens, then it will be more like a generator failure. Another example. We create a million random numbers from 1 to 100. In theory, some numbers will turn out much more, and some much less. But in practice, the quantitative discrepancy will be no more than 10 percent on all numbers. That is, not entirely by accident.
From this we see that the numbers found have some rules or conditions. The number of set bits can be from 30 to 70 percent, a sequence of up to 8 identical bits in a row, the same rotation no more than 10 times, etc. The same rules can be chosen for the 8-decimal version and the 16-decimal representation. Repeating the same numbers, ladder, etc.
And applying these rules, we can discard most of the keys so as not to check them for correctness. Yes, there may be exceptions to the rules, but most should be subject to these rules.
This increases the speed of search. And you can start not with boundary values, but let's say averaged ones.

Code:

01 - 100%, 02 - 100%, 03 - 100%, 04 - 25%, 05 - 60%, 06 - 50%, 07 - 43%, 08 - 38%, 09 - 67%, 10 - 20%, 11 - 36%, 12 - 67%, 13 - 31%, 14 - 36%, 15 - 60%, 16 - 50%, 17 - 65%, 18 - 33%, 19 - 63%, 20 - 50%,
21 - 52%, 22 - 55%, 23 - 52%, 24 - 38%, 25 - 68%, 26 - 42%, 27 - 52%, 28 - 50%, 29 - 55%, 30 - 53%, 31 - 68%, 32 - 47%, 33 - 48%, 34 - 47%, 35 - 43%, 36 - 47%, 37 - 59%, 38 - 45%, 39 - 51%, 40 - 55%,	
41 - 51%, 42 - 45%, 43 - 56%, 44 - 50%, 45 - 42%, 46 - 41%, 47 - 51%, 48 - 65%, 49 - 51%, 50 - 48%, 51 - 37%, 52 - 58%, 53 - 45%, 54 - 59%, 55 - 56%, 56 - 61%, 57 - 51%, 58 - 43%, 59 - 56%, 60 - 53%,	
61 - 48%, 62 - 55%, 63 - 57%, 65 - 45%, 70 - 49%, 75 - 44%, 80 - 46%, 85 - 46%, 90 - 48%, 95 - 51%, 100 - 53%,

Sort, less than 50 and more than 50.

Code:

01 - 100%, 02 - 100%, 03 - 100%, 05 - 60%, 09 - 67%, 12 - 67%, 15 - 60%, 17 - 65%, 19 - 63%, 
21 - 52%, 22 - 55%, 23 - 52%, 25 - 68%, 27 - 52%, 29 - 55%, 30 - 53%, 31 - 68%, 37 - 59%, 39 - 51%, 40 - 55%,	
41 - 51%, 43 - 56%, 47 - 51%, 48 - 65%, 49 - 51%, 52 - 58%, 54 - 59%, 55 - 56%, 56 - 61%, 57 - 51%, 59 - 56%, 
62 - 55%, 63 - 57%, 95 - 51%, 100 - 53%,

Count 35 Average 60,77%

Code:

04 - 25%, 07 - 43%, 08 - 38%, 10 - 20%, 11 - 36%, 13 - 31%, 14 - 36%, 18 - 33%, 
24 - 38%, 26 - 42%, 32 - 47%, 33 - 48%, 34 - 47%, 35 - 43%, 36 - 47%, 38 - 45%, 
42 - 45%, 45 - 42%, 46 - 41%, 50 - 48%, 51 - 37%, 53 - 45%, 58 - 43%, 
61 - 48%, 65 - 45%, 70 - 49%, 75 - 44%, 80 - 46%, 85 - 46%, 90 - 48%, 

Count 30 Average 41.43%

Code:

06 - 50%, 16 - 50%, 20 - 50%,
28 - 50%, 	
44 - 50%, 	

Count 5 Average 50% not used in calculation.

That is, the search can begin with a range from 41 to 61 percent.
And if we search for those already found with this range, then we will find 58 keys out of 71. That is more than 81 percent of the locations.
In this case, the search is performed in only 20 percent of the possible options, that is, 80 percent of the options recline !!!
If you have not found, increase the range, say up to 31 - 71, while also excluding options from 41 to 61 percent. Etc. Or we proceed to search for the next key.

[MrFreeDragon]

Please I Have Question to you MrFreeDragon ,Why the one who code kangaroo use CPU ,why didn't use GPU to accelerate the code and get the solution faster

I think this question should be adressed to that one who made the code kanagaroo  
But if you read some mesages before, he (or she, i can not be sure) found the last key #105, and he also wrote that he used GPU to find that one. He wrote that: "Solving #105 takes 1 month of working of GTX 1080ti at 270-275 Mh/s, and last 2 week of work of all my available GPUs (total h/s was approximately 1800Mh/s). So, it was not so simple as the Python code presented. I haven't reached published by j2002ba2 1600Mh/s. I has obtained only 470Mh/s with a cloud GPU server and one Tesla V100" (the whole post is here: https://bitcointalk.org/index.php?topic=1306983.msg52535752#msg52535752)

I use the same code of Kangaroo and I have only 10k H/s but other membres result is 100k H/s !! thats mean my cpu is low, but why not use cuda gpu ? and thanks

The 10 times difference could be because you use the phyton code to calcualte the scalar inversion. It is slow. Try to import gmpy2 library and use function gmpy2.invert - you will reach the same 100Kh/sec (depending on your CPU power). But ususaly the difference is exactly 10 times.

[bounty0z]

I think this question should be adressed to that one who made the code kanagaroo  

The 10 times difference could be because you use the phyton code to calcualte the scalar inversion. It is slow. Try to import gmpy2 library and use function gmpy2.invert - you will reach the same 100Kh/sec (depending on your CPU power). But ususaly the difference is exactly 10 times.

Thank you so much for explaining ,and sure he or she will not give the gpu code until he finish and find the key.
and about gmpy2 ,i tried to use it but can't, its problem with installing gmp and the wheel is damaged.
So now we can just go to #64 and let gpu users doing it 

[MrFreeDragon]

I think this question should be adressed to that one who made the code kanagaroo  

The 10 times difference could be because you use the phyton code to calcualte the scalar inversion. It is slow. Try to import gmpy2 library and use function gmpy2.invert - you will reach the same 100Kh/sec (depending on your CPU power). But ususaly the difference is exactly 10 times.

Thank you so much for explaining ,and sure he or she will not give the gpu code until he finish and find the key.
and about gmpy2 ,i tried to use it but can't, its problem with installing gmp and the wheel is damaged.
So now we can just go to #64 and let gpu users doing it  

It is not very difficult. Go here and download the correct version for your Python: https://www.lfd.uci.edu/~gohlke/pythonlibs/#gmpy
For eample, for python 3.7 (64bit) use this file: gmpy2-2.0.8-cp37-cp37m-win_amd64.whl
Copy that file to the root folder of your phyton, and run with administrator rights the following code: python -m pip install gmpy2-2.0.8-cp37-cp37m-win_amd64.whl

[bounty0z]

It is not very difficult. Go here and download the correct version for your Python: https://www.lfd.uci.edu/~gohlke/pythonlibs/#gmpy
For eample, for python 3.7 (64bit) use this file: gmpy2-2.0.8-cp37-cp37m-win_amd64.whl
Copy that file to the root folder of your phyton, and run with administrator rights the following code: python -m pip install gmpy2-2.0.8-cp37-cp37m-win_amd64.whl

Yeah I tried that too but still nothing,

Code:

ERROR: gmpy2-2.0.8-cp37-cp37m-win_amd64.whl is not a supported wheel on this platform.

if i use ubuntu i get that need gmp .if i tried windows i get this problem . i readed also that gmpy add 8% fast calcul.

Thanks

[MrFreeDragon]

-snip-

Code:

ERROR: gmpy2-2.0.8-cp37-cp37m-win_amd64.whl is not a supported wheel on this platform.

if i use ubuntu i get that need gmp .if i tried windows i get this problem . i readed also that gmpy add 8% fast calcul.

Thanks

You should use the same bit version (32 or 64) and the same Python version (cp37 in the file name means Python version 3.7). The error looks like you use the incorrect wheel version.