Bitcoin puzzle transaction ~32 BTC prize to who solves it

[bibilgin]

Beware of scammers, he is trying to get my 1BY8GQbnueY prefix addresses from me but doesn't have any himself and wants to offer me his 1BY8GQbnue addresses in return.
Not trustworthy

Why did you clear your Telegram conversations?

https://ibb.co/1Z3CGSr

Can you please explain why you asked me for a list and to clear your telegram conversations?

A scammer and unreliable person. He said he was an adult. I'm laughing right now. (From anger.)


The list he sent me, even though I didn't want it. I hope it helps someone.

https://privatebin.net/?0a1481abe78a7624#HkQXcLiuWmzR8oL4t9U7iqkovRNtNko96umTrj8GjP7E

@Th3_Li - Telegram Name

He keeps deleting the telegram chat so that I can show him the evidence.

[cctv5go]

I have more than ten prefixes 1BY8GQbnueYo
But unfortunately, I didn't receive the bonus.

[bibilgin]

I have more than ten prefixes 1BY8GQbnueYo
But unfortunately, I didn't receive the bonus.

I think you are talking about this wallet

1BY8GQbnueYorheQWy3zBrn72BS1UEdfDB

6xx is that correct?

[hoanghuy2912]

According to the clues I have, the private key is definitely only at 6ffffffffffffffff:7ffffffffffffffff

[bibilgin]

Hello everyone,

I wish everyone success in their work.

I said something in my previous messages.
"Every brave man eats yogurt differently."

I have met many people here and I also have private meetings.

I have never had a bad thought about anyone. For this reason, I do not LIE to anyone.

I have something to say to those who try to deceive me.
"Do you really think these things with such intelligence?"

What you want is just MONEY
What I want is bigger, your intelligence is not enough for it.

I do not want anything from anyone. I have previously told those who sent the prefix, "When I find the 67th wallet, I will send their gifts." for helping with the calculations.

Note: Valid for those between 6A... and 7D... I am not interested in other ranges. Valid only for the prefix 1BY8GQbnue or 1BY8GQbnueY.

I wish everyone good luck and good work.

[pbies]

to waste time.
simple python code for puzzle 66.
it is extremely slow but to learn what we are looking for..

Code:

import hashlib
import time
import base58
import threading
import keyboard  # For detecting key press events
from bitcoinlib.keys import Key

print("Starting scan, hit x to exit...")

# Function to check if the private key corresponds to the Bitcoin address
def check_private_key_for_address(private_key_hex, expected_address):
    # Convert the private key hex to WIF format (compressed)
    wif_private_key = hex_to_wif(private_key_hex, compressed=True)
    
    # Create a Key object from the WIF private key
    key = Key.from_wif(wif_private_key)
    
    # Generate the compressed Bitcoin address from the private key (P2PKH)
    generated_address = key.address('p2pkh')
    
    # Compare the generated address with the expected address
    if generated_address == expected_address:
        return private_key_hex, generated_address
    return None

# Function to convert a hex private key to WIF (compressed)
def hex_to_wif(private_key_hex, compressed=True):
    # Convert hex to bytes
    private_key_bytes = bytes.fromhex(private_key_hex)
    
    # WIF requires the mainnet prefix 0x80 for a mainnet key
    version_byte = b'\x80'
    extended_key = version_byte + private_key_bytes
    
    # Add 0x01 byte at the end if compressed
    if compressed:
        extended_key += b'\x01'
    
    # Create checksum for WIF format
    checksum = hashlib.sha256(hashlib.sha256(extended_key).digest()).digest()[:4]
    
    # Convert to base58 and return the WIF format
    wif = base58.b58encode(extended_key + checksum).decode('utf-8')
    
    return wif

# Function to listen for the 'X' key press in a separate thread
def listen_for_stop():
    global stop_flag
    while True:
        if keyboard.is_pressed('x'):  # When 'x' is pressed
            print("Stopping search...")
            stop_flag = True
            break

# Function to process a range of keys in a separate thread
def process_key_range(start_value, end_value, expected_address, file):
    global stop_flag, match_found
    total_keys = 0
    start_time = time.time()
    
    for value in range(start_value, end_value + 1):
        if stop_flag or match_found:  # Check if the search should be stopped
            return
        
        private_key_hex = hex(value)[2:].zfill(64)  # Convert to hex and pad to 64 characters
        result = check_private_key_for_address(private_key_hex, expected_address)
        
        if result:
            private_key_hex, expected_address = result
            print(f"MATCH!")
            print(f"private_key_hex: {private_key_hex}")
            print(f"expected_address: {expected_address}")
            
            # Write the match to 'found.txt'
            with open('found.txt', 'a') as file:
                file.write(f"MATCH!\nprivate_key_hex: {private_key_hex}\nexpected_address: {expected_address}\n\n")
            
            match_found = True  # Mark match found
            stop_flag = True  # Stop all other threads
            return
        
        total_keys += 1
        
        # Every 30 seconds, print speed (keys/sec)
        if time.time() - start_time >= 30:
            elapsed_time = time.time() - start_time
            speed = total_keys / elapsed_time  # Keys per second
            print(f"Speed: {speed:.2f} keys/sec")
            start_time = time.time()  # Reset the timer
            total_keys = 0  # Reset the count of keys processed in the last 30 seconds

# Expected address to match
expected_address = "13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so"  # Compressed address

# Range of private keys to search
start_value = 0x2832ed74f2b5c0000
end_value = 0x5ffffffffffffffff

# Global flags
stop_flag = False
match_found = False  # Flag to indicate if a match is found

# Start the listener for key press in a separate thread
listener_thread = threading.Thread(target=listen_for_stop)
listener_thread.daemon = True
listener_thread.start()

# Open the 'found.txt' file in append mode to store matched results
with open('found.txt', 'a') as file:
    threads = []
    num_threads = 1  # Adjust the number of threads as necessary
    range_size = (end_value - start_value + 1) // num_threads
    
    # Divide the range into multiple chunks and assign each chunk to a thread
    for i in range(num_threads):
        thread_start = start_value + i * range_size
        thread_end = start_value + (i + 1) * range_size - 1
        if i == num_threads - 1:  # Ensure the last thread processes the remaining range
            thread_end = end_value
        
        # Start the thread for the given range
        thread = threading.Thread(target=process_key_range, args=(thread_start, thread_end, expected_address, file))
        threads.append(thread)
        thread.start()

    # Wait for all threads to finish or for a match to be found
    for thread in threads:
        thread.join()

    if match_found:
        print("Match found! Exiting.")
    elif stop_flag:
        print("Search stopped by user.")
    else:
        print("Private key does not match the address in the given range.")

Really?

222 keys per second with 16 threads?

Are you kidding me?

[dibzzy]

its only for to show and learn how the process is done using one thread.
feel free to optimize but its impossible to gain speed with python.
using opencl makes no difference.
that is why to use C..

here's a simple one i made in python .. does about 35-50k keys/s deppending on cpu https://github.com/dibzzy/Easy-Bitcoin-puzzle-key-scanner

[iceland2k14]

I still don't understand why people are searching for the Prefix 1BY8GQbnue . It does not give any advantage towards the full solution, no matter what anyone believes.

[Kelvin555]

I still don't understand why people are searching for the Prefix 1BY8GQbnue . It does not give any advantage towards the full solution, no matter what anyone believes.

It gives an advantage towards the full solution for some other people but not in the way the people searching for the prefixes think.

[saatoshi_falling]

I would not have thought the year 2025 would be the war of the prefixes.
You guys really need to understand this. You literally change 1 character and the prefix has no use. 1BY8GQbnuXX can be at the start of the range, while 1BY8GQbnuXXY can be at the very end of the range. There's no link. You can't reverse it. I'm having a hard time to even express this because it's such a stupid idea.
I won't be contributing to this thread until Bitcoin leaves the 100k quack range and reaches 59k what I call the "sanity range" where more normal theories are being discussed.

[Jorge54PT]

Everyone comments on everyone's methods, but what I know is that 67 is still intact

[mcdouglasx]

I would not have thought the year 2025 would be the war of the prefixes.
You guys really need to understand this. You literally change 1 character and the prefix has no use. 1BY8GQbnuXX can be at the start of the range, while 1BY8GQbnuXXY can be at the very end of the range. There's no link. You can't reverse it. I'm having a hard time to even express this because it's such a stupid idea.
I won't be contributing to this thread until Bitcoin leaves the 100k quack range and reaches 59k what I call the "sanity range" where more normal theories are being discussed.

What I understand here is the following: 1. They gather a series of prefixes and catalog them to average the distances between each prefix (pattern). 2. They search by probability in the approximate ranges to the next possible pattern.
Since the puzzle is in a small range compared to 256 bits, it is not unreasonable to use predictions, although it is not precise, it has its logic.

[kTimesG]

I would not have thought the year 2025 would be the war of the prefixes.
You guys really need to understand this. You literally change 1 character and the prefix has no use. 1BY8GQbnuXX can be at the start of the range, while 1BY8GQbnuXXY can be at the very end of the range. There's no link. You can't reverse it. I'm having a hard time to even express this because it's such a stupid idea.
I won't be contributing to this thread until Bitcoin leaves the 100k quack range and reaches 59k what I call the "sanity range" where more normal theories are being discussed.

What I understand here is the following: 1. They gather a series of prefixes and catalog them to average the distances between each prefix (pattern). 2. They search by probability in the approximate ranges to the next possible pattern.
Since the puzzle is in a small range compared to 256 bits, it is not unreasonable to use predictions, although it is not precise, it has its logic.

Yeah, this is why the thread has become the daily journal of "prefix of the day". The guy who started this daily blog was first under the impression that there are only 4 prefixes of some kind, and he then was proven wrong (correct value was somewhere around 1000 prefixes). And now we're all anxiously watching his catalog progress, one prefix at a time, for years to come.

I would laugh so hard to know that the real answer to 67 is just a few keys away from an already found prefix, in a range that was definitely dismissed because someone thinks he can outsmart a random noise distribution.

[bibilgin]

Yeah, this is why the thread has become the daily journal of "prefix of the day". The guy who started this daily blog was first under the impression that there are only 4 prefixes of some kind, and he then was proven wrong (correct value was somewhere around 1000 prefixes). And now we're all anxiously watching his catalog progress, one prefix at a time, for years to come.

I would laugh so hard to know that the real answer to 67 is just a few keys away from an already found prefix, in a range that was definitely dismissed because someone thinks he can outsmart a random noise distribution.

Yes, KTimesG I think you didn't understand. Your other friends may be confused.

The 4 intervals with the prefix 1BY8GQbnueY are important to me.
(Between 6A... and 7D...)

I determine the AVERAGE interval of the 1BY8GQbnue prefixes with my PROBABILITY and MATHEMATICAL calculations.

Are you saying that the 1BY8GQbnueY prefix is ​​over 1000?
Be patient a little longer, as I said when it is finished I will share the Hex code, SHA256 and SHA512.

[hotmoney]

THERE ARE MULTIPLE COMBINATIONS THESE ADDRESSES EXIST WE JUST DON'T HAVE THEIR PRIVATE KEYS YET BUT THERE ARE ENDLESS COMBINATIONS... I FOUND THESE THIS MONTH

Someone send me some money to help with energy I will continue publishing but addresses thank you      my address donate       1ericoPSxFdQWGAE6iDcdc2jc3HBRYpEC

PubAddress: 1BY8GQbnu1DPVT6c66yLZRvMRcugu41i4v
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qb1BpUpTPTMZvzTW6w38
Priv (HEX): 62AD2731CC3285DB2 (67 bit)

PubAddress: 1BY8GQbnu6v7Ux8krR8URwodBWm1SawLnr
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qb1AmPhsuXNqMapR1bpb
Priv (HEX): 62A9AA2EB577A9FF8 (67 bit)

PubAddress: 1BY8GQbnu8jSXMYE4o2ZfzFSv3D7fX7BGC
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qatTWrxLTZsfBbss3EQ2
Priv (HEX): 5DA0791C09C3BBAC4 (67 bit)

PubAddress: 1BY8GQbnu9Pr3u4dLhGZo2vCrQswS8fZTz
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qabYU6bF3ZDDBjJh2kNQ
Priv (HEX): 50EF4226B89DF60AA (67 bit)

PubAddress: 1BY8GQbnub1JKjz49sq9NhHUXVjujDNXFp
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qawb2V4cHnNNhpXYUVP1
Priv (HEX): 5FF9A24218EA189F4 (67 bit)

PubAddress: 1BY8GQbnucXmpBfXmSaqrYfmyE8v2dh2uA
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qaccTEqzmmLtkcQBnFEz
Priv (HEX): 51BC8D6E6A141E38D (67 bit)

PubAddress: 1BY8GQbnuGbW7BppF1HchbeneV2gG1Gh7B
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qakTBCawW4YR6tnWw8UX
Priv (HEX): 579E96EC070A54893 (67 bit)

PubAddress: 1BY8GQbnugVjgeL43mD1SqXpAFU8mqSE5R
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qaTR8PhQPcePBUvstdff
Priv (HEX): 4AD6304048C00378A (67 bit)

PubAddress: 1BY8GQbnujgvke9PYWMpNbwTs9Jdvv7KTe
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qaZ5BRtJYKA7J2VEVaaa
Priv (HEX): 4F14B15F5AE4EF20A (67 bit)PubAddress: 1BY8GQbnuy3wbCC9Gorrhi6PijfdRjtQXT

Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qai7oV99TmLWDasNfzvh
Priv (HEX): 55DE3B4E1A5DEFA73 (67 bit)



1BY8GQbnueY1 xxxxxx
1BY8GQbnueY2 xxxxxx
1BY8GQbnueY3 xxxxxx
1BY8GQbnueY4 xxxxxx
1BY8GQbnueY5 xxxxxx
1BY8GQbnueY6 xxxxxx
1BY8GQbnueY7 xxxxxx
1BY8GQbnueY8 xxxxxx
1BY8GQbnueY9 xxxxxx
1BY8GQbnueY0 xxxxxx

1BY8GQbnueY1A xxxxx
1BY8GQbnueY1a xxxxx

1BY8GQbnueY1B xxxxx
1BY8GQbnueY1b xxxxx

1BY8GQbnueYC xxxx
1BY8GQbnueY1c xxxx  


1BY8GQbnueA
1BY8GQbnuea

1BY8GQbnueB
1BY8GQbnueb

1BY8GQbnueC
1BY8GQbnuec

1BY8GQbnueD
1BY8GQbnued

1BY8GQbnueE
1BY8GQbnuee

1BY8GQbnueF
1BY8GQbnuef

1BY8GQbnueG
1BY8GQbnueg

1BY8GQbnueH
1BY8GQbnueh

1BY8GQbnueI
1BY8GQbnuei

1BY8GQbnueJ
1BY8GQbnuej

1BY8GQbnueK
1BY8GQbnuek

1BY8GQbnueL
1BY8GQbnuel

1BY8GQbnueM
1BY8GQbnuem

1BY8GQbnueN
1BY8GQbnuen

1BY8GQbnueO
1BY8GQbnueo

1BY8GQbnueP
1BY8GQbnuep

1BY8GQbnueQ
1BY8GQbnueq

1BY8GQbnueR
1BY8GQbnuer

1BY8GQbnueS
1BY8GQbnues

1BY8GQbnueT
1BY8GQbnuet

1BY8GQbnueU
1BY8GQbnueu

1BY8GQbnueV
1BY8GQbnuev

1BY8GQbnueW
1BY8GQbnuew

1BY8GQbnueX
1BY8GQbnuex

1BY8GQbnueY
1BY8GQbnuey

1BY8GQbnueZ
1BY8GQbnuez


1BY8GQbnueA
1BY8GQbnuea

1BY8GQbnueB
1BY8GQbnueb

1BY8GQbnueC
1BY8GQbnuec

1BY8GQbnueD
1BY8GQbnued

1BY8GQbnueE
1BY8GQbnuee

1BY8GQbnueF
1BY8GQbnuef

1BY8GQbnueG
1BY8GQbnueg

1BY8GQbnueH
1BY8GQbnueh

1BY8GQbnueI
1BY8GQbnuei

1BY8GQbnueJ
1BY8GQbnuej

1BY8GQbnueK
1BY8GQbnuek

1BY8GQbnueL
1BY8GQbnuel

1BY8GQbnueM
1BY8GQbnuem

1BY8GQbnueN
1BY8GQbnuen

1BY8GQbnueO
1BY8GQbnueo

1BY8GQbnueP
1BY8GQbnuep

1BY8GQbnueQ
1BY8GQbnueq

1BY8GQbnueR
1BY8GQbnuer

1BY8GQbnueS
1BY8GQbnues

1BY8GQbnueT
1BY8GQbnuet

1BY8GQbnueU
1BY8GQbnueu

1BY8GQbnueV
1BY8GQbnuev

1BY8GQbnueW
1BY8GQbnuew

1BY8GQbnueX
1BY8GQbnuex

1BY8GQbnueY
1BY8GQbnuey

1BY8GQbnueZ
1BY8GQbnuez

[bibilgin]

THERE ARE MULTIPLE COMBINATIONS THESE ADDRESSES EXIST WE JUST DON'T HAVE THEIR PRIVATE KEYS YET BUT THERE ARE ENDLESS COMBINATIONS... I FOUND THESE THIS MONTH

This month?

I can find all of these in 1 day, even in half a day.

[bitcoinpuzzles621]

A long time ago, I would think that the prefixes were important too and that I could somehow use them in my code.  But eventually I just realized they dont help very much.  Its still all just a random search space and the solution could still be anywhere.  My code though is also terrible and can only find 1BY8G prefixes most days.  So you guys are far ahead of me in your progress if you believe that the longer prefixes are important.   I just am trying to say that I dont believe they are as important anymore.  I am more in agreement with the skeptics that post here recently about the prefixes instead.   

[hotmoney]

bibilgin  How so, Bibilgin? I use an RTX 4060, and it goes to 1320 MH/s overclocked. Which card do you use, Bibilgin?

[b0dre]

I can find all of these in 1 day, even in half a day.

Which tools are you using?

[hotmoney]

I discovered last month the correct way to transfer without being robbed, without RBF. The method I use to transfer funds from wallets with 66 to 70 bits—I tested everything, especially 67—works with the method I created, without Marapool or Electrum. And it works. I even tried to steal from myself, and I had friends with powerful cards try

as well. I made the transfer, and 10 friends tried to steal from me, but it didn’t work. Even I tried to do an RBF, but it doesn’t replace the transaction, no matter how high I set the fee.

I found the flaw that allows thieves to steal, and if you use my method, it prevents this. If anyone wants to test with me, just let me know—I’m available. Forget Marapool and forget mining your own blocks. This is the only way I’ve managed to make it work.  I set a super low fee, and it stayed there for about 17 minutes, and no one

managed to steal it—not even I was able to replace the transaction. The only way to accelerate it was by doing a CPFP (Child Pays for Parent) on the receiver's side, and that’s it.  f anyone wants to test with me or talk to me, feel free. I had to study a lot to achieve this. Currently, I’m using a Raspberry Pi and some additional tools to make the

transfer. No boot has been able to steal from me—I’ve even tested it in under 5 seconds, and it doesn’t perform an RBF or manage to replace the transaction.

If anyone wants to test with me today, I can transfer $10 for you to try and steal it with your boots. I'll create a 67-bit key and share the address with you, okay? You can get the public key from the mempool with your bots, but you won’t be able to steal it.

Does anyone want to collaborate with a few dollars to do this today? I’ll leave the wallet here—I'll do it at 10 PM tonight. I'm in Uruguay, sorry for my bad English.

This will be the wallet (67-bit):

1BY8GQbBPGYEC58s9ckHmqf9doEX9mCKPR

Let me know who will try to steal it today and who will send some funds to this wallet!