<<  >> (p.162)
    Author Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it  (Read 324836 times)
    sssergy2705
    Copper Member
    Jr. Member
    *
    Offline Offline

    Activity: 205
    Merit: 1


    View Profile
    August 19, 2023, 08:00:02 AM
     #3221

    Just info.

    Think in your own way and your own point of view about this WIF range

    Do we have GPU crackers for WIF Private Keys? or do we have someone that can build 1? these have more potentials for brute forcing puzzle 66 from the Random Point of view for probably the last 16 - 18 characters ranges scanned sequentially, compared to the hexadecimal private keys because of the checksum involved in the WIF Private keys... this might be it, every hexadecimal key is valid but not all WIFs are which brings us to the point where scanning might be fun to play with

    What is the point of this if what you see in every row is just representation of padded zeros?

    That is the point right there "padded zeros" as explained earlier, the hexadecimal is just from 0 to F base16 whereas the WIF is a base58 equivalent of that base 16 hexadecimal representation... so what point does this make? Well, I can have 3.625 of the hexadecimal character represented as just 1 character of the WIF... this in otherwords simply means if you are able to hit the correct first 3 WIF characters, then you probably don't have too much range to scan compared to hitting the correct first 3 characters of the hexadecimal representation of the same key... you've got a long way to go bro... So i See some potentials in this WIF bruteforcing for the puzzle 66

    Key search range 66
    KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q ZVfMsBQggk69993Lj3p
    KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3q aCtgAeZDbST4e5pMroG

    We can't do anything with this information.
    In fact, it will be the same brute force of keys. There is no difference in what format to sort through the keys, even in binary, even in hex, even in base58.


    How you can explain this ?

    Puzzle 118 address is 1PJZPzvGX19a7twf5HyD2VvNiPdHLzm9F6

    this is the 0000000000000000000000000000000000af0f4d11574f5deee49961d9609ac6 address 1PEuXxTXfc3qJM4H7EKRbSb8TSPFtds9A5

    Public key 02bc5f15678ceb70dad97a6b695b9e0df7c405142586931801c2df664563042fe7

    I just random search WIF range on that, and i have lock the range area by Hex padded.

    yeah it's suck it's like 0.0000001% chance hit the 4 same HEX value WIF.


    [EDIT 10:41 Indonesia Time]

    Target

    1PJZPzvGX19a7twf5HyD2VvNiPdHLzm9F6 # 118

    this, i found 3 word same address range, from range padded hex.

    031e841aa39d5d92ae850400a2d8be24a245d53e9ba29dc86b86696e65290c32d7 = 1PJgNwNbpr1KRxdmPxPXMCWqdBT1bwgDEe

    The public address has no binding either to the public key or to the private key.
    You need to carefully study the process of obtaining bitcoin addresses.
Page 161
Viewing Page: 162