Bitcoin

There are people who just want to see the world burn, in this case i'm talking about bicoin-haters they send bitcoin to address that are made just to burn the bitcoin balance. What means burn bitcoin? Well there are some address with "unknow" private key, this is because nobody knows what is the private key of those address, so if you send some bitcoin to this addresses that mean that may be nobody is going to be able to use those address in the future. I will try to make an exhaustive list but just addresses with technical information, just to know why those addresses are may be "un-spendable". But remember every bitcoin address have in theory 2^96 private keys,  this mean that exist almost (79228162514264337593543950336 private keys for every bitcoin address) . Total of burned bitcoin in this list 3373.04576273 BTC Address: 15wJjXvfQzo3SXqoWGbWZmNYND1Si4siqV  Balance: 0.00664516 BTC Reason: This address may be un-spendable because is the result of address_from

What is a WIF? R: Wallet Import Format You can found more details of a wif in  Chapter 4. Keys, Addresses, Wallets Solving WIF can be an impossible task or maybe an easy one all depend of what kind of data do you have. There are some different scenarios Missing characters at the end. Missing characters in the middle Missing characters in the beginning. Each case have different approach to solve it. Also we need to considerate the next questions: Where the WIF come from? If the data of the WIF was taken from some YouTube video or some public picture on internet, please FORGET it, most of the WIF KEY from public internet sources are fake, just made to troll people. How many missing characters are there? If the amount of missing characters are near to the half of the WIF please also forget that WIF even if the WIF is real is near to impossible brute force the  missing characters. Missing characters at the end is the most easy case to solve because at the end of the WIF we have the checksu

The valid bitcoin base58 charset is  123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz Today someone send to me a partial WIF to crack it,, but in middle of the key was some "I" or "l" and none of those both characters are in the base58 charset. Just look the image below:

I love to read the history of the previous puzzles solved, in this occasion we have the 70 bit puzzle solved by Unknown   In the next post ( Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it ) the user  arulbero  write that solve the puzzle 70 in his server took near to 12 hrs, here i need to mention that he don't solve originally the puzzle, he only was trying to get the private key for to keep it for the record of the puzzles. Here is the message: He write "It took almost 12 hours to find the #70 on my system (Intel® Xeon® CPU E3-1505M v6 @ 3.00GHz + 32 GB RAM). No GPU, only CPU (1 core, my program is not multithread)." Points to considerate: I understand that "almost 12 hours" should be somethin between 11 and 12 hours I don't know if he using all the 32 GB of RAM Only One thread No GPU I as the developer of keyhunt I try to compare Apples with apples here is keyhunt solving the 70 bit puzzle The result for keyhunt was better because It solve

 I will try to keep an update list with the current unsolved puzzles or challenges. Challenges In January 15, 2015 a especial transaction was made in the bitcoin network, that transactions was  exactly 32.9 Bitcoin send to 256 address, tx hash  08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 Those 256 were one address in each bit range. But in the year 2017 the author move all the founds from address above the 161 bit space up to the 256 bit space to the lower puzzles. Incrementing the balance of the remaining puzzles under the 160 bit puzzle. This is the only one message of the author: The amount total for this puzzle is 98.74 Bitcoin , the list of the address with balance is the next: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9 1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ 19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU 1JTK7s9YVYywfm5XUH7RNhHJH1LshCaRFR 12VVRNPi4SJqUTsp6FmqDqY5sGosDtysn4