didn't understand

[unclevito2017]

didn't understand

[unclevito2017]

Ok lets say we are looking for the private key for 1K2wh7bdCYgFeipT8fnCS3GknWLKHPgJq5 as an example in 66 . Usually we don't know the private key so the script generates 7 random hex digits and puts them at the end of the start range that bitcrack will search through. the script selects 7 random hex digits writes them to the tried.txt file and starts bitcrack. If these 7 hex digits are the correct that are part of the 17 hex digits that make up the private key for the public address above the program will figure out the first 10 hex digits and write the complete private key for that address in the found.txt. If the 7 hex digits are not correct it will generate 7 new hex digits and try again. this process will keep going until the correct hex digits are tried or the program is stopped. The tried.txt is used to store the tried hex digits and each time it generates 7 new hex digits it checks the tried.txt so it does not try the same 7 twice, no repeats. The example I gave is just to show the theory behind the program and that it can find the complete 17 hex digits if the 7 are correct. We know the test address 1K2wh7bdCYgFeipT8fnCS3GknWLKHPgJq5 has a private key 3E838B13505B26867 and the last 7 hex are 5B26867 so just to show that bitcrack can solve this address with the last 7 hex we run bitcrack from the command line BitCrack.exe -b 128 -t 256 -p 1380 --stride 100000000 --keyspace 20000000005b26867:3ffffffffffffffff -o FOUND.txt -c 1K2wh7bdCYgFeipT8fnCS3GknWLKHPgJq5 . Doing this s just to show bitcrack can solve with just 7 hex. But we are looking for 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so and unlike the test address above we have no idea what the last 7 hex re so we run the script python3 p66.py for windows the script generates 7 random hex and runs bitcrack to see if they are the correct 7 if not checks tried.txt and tries another 7 hex, over and over until found or you quit, the address is built into the python script.Each time it runs it assigns a new 7 hex pattern to try. Remember Bitcrack.exe has to be in the same folder as p66.py or if linux cuBitCrack with pattern66.py .
To run in windows:
python3 p66.py
Pattern: 85B842E
[2023-09-17.21:21:50] [Info] Compression : compressed
[2023-09-17.21:21:50] [Info] Starting at : 00000000000000000000000000000000000000000000000200000000085B842E (66 bit)
[2023-09-17.21:21:50] [Info] Ending at : 000000000000000000000000000000000000000000000003FFFFFFFFFFFFFFFF (66 bit)
[2023-09-17.21:21:50] [Info] Range : 000000000000000000000000000000000000000000000001FFFFFFFFF7A47BD1 (65 bit)
[2023-09-17.21:21:50] [Info] Initializing NVIDIA GeForce RTX 3060 Ti
[2023-09-17.21:21:50] [Info] Generating 44,040,192 starting points (1680.0MB)
[2023-09-17.21:22:10] [Info] 10.0% 20.0% 30.0% 40.0% 50.0% 60.0% 70.0% 80.0% 90.0% 100.0%
[2023-09-17.21:22:12] [Info] Done
[DEV: NVIDIA GeForce R 7773/8191MB] [0000000000000000000000000000000000000000000000025BE00000085B842E (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 850.20 MKey/s] [TOTAL: 1,5[DEV: NVIDIA GeForce R 7773/8191MB] [000000000000000000000000000000000000000000000002B7C00000085B842E (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 850.67 MKey/s] [TOTAL: 3,0[DEV: NVIDIA GeForce R 7773/8191MB] [00000000000000000000000000000000000000000000000313A00000085B842E (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 850.67 MKey/s] [TOTAL: 4,6[DEV: NVIDIA GeForce R 7773/8191MB] [0000000000000000000000000000000000000000000000036F800000085B842E (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 843.22 MKey/s] [TOTAL: 6,1[DEV: NVIDIA GeForce R 7773/8191MB] [000000000000000000000000000000000000000000000003CB600000085B842E (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 835.90 MKey/s] [TOTAL: 7,707,033,600] [00:00:07][2023-09-17.21:22:23] [Info] Reached end of keyspace
Pattern: 942A058
[2023-09-17.21:22:40] [Info] Compression : compressed
[2023-09-17.21:22:40] [Info] Starting at : 000000000000000000000000000000000000000000000002000000000942A058 (66 bit)
[2023-09-17.21:22:40] [Info] Ending at : 000000000000000000000000000000000000000000000003FFFFFFFFFFFFFFFF (66 bit)
[2023-09-17.21:22:40] [Info] Range : 000000000000000000000000000000000000000000000001FFFFFFFFF6BD5FA7 (65 bit)
[2023-09-17.21:22:40] [Info] Initializing NVIDIA GeForce RTX 3060 Ti
[2023-09-17.21:22:40] [Info] Generating 44,040,192 starting points (1680.0MB)
[2023-09-17.21:23:00] [Info] 10.0% 20.0% 30.0% 40.0% 50.0% 60.0% 70.0% 80.0% 90.0% 100.0%
[2023-09-17.21:23:02] [Info] Done
[DEV: NVIDIA GeForce R 7773/8191MB] [0000000000000000000000000000000000000000000000025BE000000942A058 (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 850.67 MKey/s] [TOTAL: 1,5[DEV: NVIDIA GeForce R 7773/8191MB] [000000000000000000000000000000000000000000000002B7C000000942A058 (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 835.90 MKey/s] [TOTAL: 3,0[DEV: NVIDIA GeForce R 7773/8191MB] [00000000000000000000000000000000000000000000000313A000000942A058 (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 843.22 MKey/s] [TOTAL: 4,6[DEV: NVIDIA GeForce R 7773/8191MB] [0000000000000000000000000000000000000000000000036F8000000942A058 (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 835.90 MKey/s] [TOTAL: 6,1[DEV: NVIDIA GeForce R 7773/8191MB] [000000000000000000000000000000000000000000000003CB6000000942A058 (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 836.36 MKey/s] [TOTAL: 7,707,033,600] [00:00:07][2023-09-17.21:23:13] [Info] Reached end of keyspace

[sari777]

thanks for explaining. i was confused. good.

[sari777]

on other hand why people depositing small amounts to puzzle 66.? any idea.?
is there any kind of other attacks.? dust attack.?
to recover the public key.? then keyhunt will easily target the key.?

[unclevito2017]

Probably dust attacks by someone or a few different scammers who are waiting for 66 to get solved so they can trace and figure out who solved 66 when it finally gets solved and try to steal the bitcoin. It could also be a government agency like the IRS in the USA trying to track the crypto in case someone wins the 6.6 bitcoins and tries not to pay taxes, they are not scammers but are parasites . The only way a public key could be generated is if 66 sent some crypto so it's not that. So far sent to 66 has 0 value so it looks like dust. But someone may be working on a way to crack 66 with multiple transaction hashes, who knows, there are a lot of smart people in the crypto game

…

On Mon, Sep 18, 2023 at 11:33 AM sari777 ***@***.***> wrote: on other hand why people depositing small amounts to puzzle 66.? any idea.? is there any kind of other attacks.? dust attack.? to recover the public key.? then keyhunt will easily target the key.? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI3P53L7X75M5XKE53LU223X3BSTTANCNFSM6AAAAAA43WYAKM> . You are receiving this because you commented.Message ID: ***@***.*** com>

[sari777]

Probably dust attacks by someone or a few different scammers who are waiting for 66 to get solved so they can trace and figure out who solved 66 when it finally gets solved and try to steal the bitcoin. It could also be a government agency like the IRS in the USA trying to track the crypto in case someone wins the 6.6 bitcoins and tries not to pay taxes, they are not scammers but are parasites . The only way a public key could be generated is if 66 sent some crypto so it's not that. So far sent to 66 has 0 value so it looks like dust. But someone may be working on a way to crack 66 with multiple transaction hashes, who knows, there are a lot of smart people in the crypto game
…
On Mon, Sep 18, 2023 at 11:33 AM sari777 @.> wrote: on other hand why people depositing small amounts to puzzle 66.? any idea.? is there any kind of other attacks.? dust attack.? to recover the public key.? then keyhunt will easily target the key.? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI3P53L7X75M5XKE53LU223X3BSTTANCNFSM6AAAAAA43WYAKM . You are receiving this because you commented.Message ID: @. com>

Thanks sir for guide.