Bitcoin puzzle transaction ~32 BTC prize to who solves it

[nomachine]

you need to know the compressed publickey hex66 to run.
However I don't know how to get this.

This is where the fun both begins and ends for fools.



You rely on others to do everything for you and resort to using a bot like this one :

Code:

import requests
import time
import subprocess
import os
import secp256k1 as ice
import json

def check_public_key():
    url = "https://blockchain.info/q/pubkeyaddr/13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so"
    response = requests.get(url)
    
    if response.status_code == 200:
        data = response.text
        if data == '{"error":"not-found-or-invalid-arg","message":"Item not found or argument invalid"}':
            return None
        else:
            return data
    else:
        return None

def save_public_key(pubkey):
    with open("66.txt", "w") as f:
        f.write(pubkey)

def run_keyhunt():
    command = "./keyhunt -m bsgs -f 66.txt -b 66 -q -s 10 -S -t 128 -k 4096 -S"
    subprocess.run(command, shell=True)

def extract_private_key():
    with open("KEYFOUNDKEYFOUND.txt", "r") as f:
        for line in f:
            if "Key found privkey" in line:
                privkey = line.split("Key found privkey")[1].strip()
                return privkey
    return None

def convert_to_wif(privkey):
    return ice.btc_pvk_to_wif(privkey)

def start_electrum_daemon():
    command = "electrum daemon -d"
    subprocess.run(command, shell=True)

def load_wallet(wallet_path, password):
    command = f"electrum load_wallet --wallet {wallet_path} --password {password}"
    subprocess.run(command, shell=True)

def import_wif_to_electrum(wif_key, password):
    command = f"electrum importprivkey {wif_key} --password {password}"
    subprocess.run(command, shell=True)

def list_txids():
    command = "electrum listunspent"
    result = subprocess.run(command, shell=True, capture_output=True, text=True)
    unspent = json.loads(result.stdout)
    return [utxo['tx_hash'] for utxo in unspent]

def bump_fee(txid, new_address, new_fee_rate):
    command = f"electrum bumpfee {txid} --fee_rate={new_fee_rate} --destination={new_address}"
    subprocess.run(command, shell=True)

def main():
    wallet_path = "/root/.electrum/wallets/default_wallet" # Replace with your path
    wallet_password = "Satoshi" # Wallet password
    new_address = "NEW_BTC_ADDRESS_HERE"  # Replace with the desired destination address
    new_fee_rate = 0.04  # Fee rate in BTC/kB (set to 0.04 or whatever you want)
    
    while True:
        pubkey = check_public_key()
        if pubkey:
            save_public_key(pubkey)
            run_keyhunt()
            if os.path.exists("KEYFOUNDKEYFOUND.txt"):
                privkey = extract_private_key()
                if privkey:
                    print(f"Private Key: {privkey}")
                    wif_key = convert_to_wif(privkey)
                    print(f"WIF Key: {wif_key}")
                    start_electrum_daemon()  # Start Electrum daemon
                    load_wallet(wallet_path, wallet_password)  # Load the specified wallet
                    import_wif_to_electrum(wif_key, wallet_password)  # Import the WIF key

                    # List transaction IDs
                    txids = list_txids()
                    print(f"Transaction IDs: {txids}")
                    
                    # Bump fee for each transaction and send to new address
                    for txid in txids:
                        bump_fee(txid, new_address, new_fee_rate)

                    break
        # Sleep for 60 seconds before checking the URL again
        time.sleep(60)

if __name__ == "__main__":
    main()

[maylabel]

you need to know the compressed publickey hex66 to run.
However I don't know how to get this.

This is where the fun both begins and ends for fools.

https://media1.tenor.com/m/rQ4TZYm3GJEAAAAC/yes-evil.gif

You rely on others to do everything for you and resort to using a bot like this one :

Code:

import requests
import time
import subprocess
import os
import secp256k1 as ice
import json

def check_public_key():
    url = "https://blockchain.info/q/pubkeyaddr/13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so"
    response = requests.get(url)
    
    if response.status_code == 200:
        data = response.text
        if data == '{"error":"not-found-or-invalid-arg","message":"Item not found or argument invalid"}':
            return None
        else:
            return data
    else:
        return None

def save_public_key(pubkey):
    with open("66.txt", "w") as f:
        f.write(pubkey)

def run_keyhunt():
    command = "./keyhunt -m bsgs -f 66.txt -b 66 -q -s 10 -S -t 128 -k 4096 -S"
    subprocess.run(command, shell=True)

def extract_private_key():
    with open("KEYFOUNDKEYFOUND.txt", "r") as f:
        for line in f:
            if "Key found privkey" in line:
                privkey = line.split("Key found privkey")[1].strip()
                return privkey
    return None

def convert_to_wif(privkey):
    return ice.btc_pvk_to_wif(privkey)

def start_electrum_daemon():
    command = "electrum daemon -d"
    subprocess.run(command, shell=True)

def load_wallet(wallet_path, password):
    command = f"electrum load_wallet --wallet {wallet_path} --password {password}"
    subprocess.run(command, shell=True)

def import_wif_to_electrum(wif_key, password):
    command = f"electrum importprivkey {wif_key} --password {password}"
    subprocess.run(command, shell=True)

def list_txids():
    command = "electrum listunspent"
    result = subprocess.run(command, shell=True, capture_output=True, text=True)
    unspent = json.loads(result.stdout)
    return [utxo['tx_hash'] for utxo in unspent]

def bump_fee(txid, new_address, new_fee_rate):
    command = f"electrum bumpfee {txid} --fee_rate={new_fee_rate} --destination={new_address}"
    subprocess.run(command, shell=True)

def main():
    wallet_path = "/root/.electrum/wallets/default_wallet" # Replace with your path
    wallet_password = "Satoshi" # Wallet password
    new_address = "NEW_BTC_ADDRESS_HERE"  # Replace with the desired destination address
    new_fee_rate = 0.04  # Fee rate in BTC/kB (set to 0.04 or whatever you want)
    
    while True:
        pubkey = check_public_key()
        if pubkey:
            save_public_key(pubkey)
            run_keyhunt()
            if os.path.exists("KEYFOUNDKEYFOUND.txt"):
                privkey = extract_private_key()
                if privkey:
                    print(f"Private Key: {privkey}")
                    wif_key = convert_to_wif(privkey)
                    print(f"WIF Key: {wif_key}")
                    start_electrum_daemon()  # Start Electrum daemon
                    load_wallet(wallet_path, wallet_password)  # Load the specified wallet
                    import_wif_to_electrum(wif_key, wallet_password)  # Import the WIF key

                    # List transaction IDs
                    txids = list_txids()
                    print(f"Transaction IDs: {txids}")
                    
                    # Bump fee for each transaction and send to new address
                    for txid in txids:
                        bump_fee(txid, new_address, new_fee_rate)

                    break
        # Sleep for 60 seconds before checking the URL again
        time.sleep(60)

if __name__ == "__main__":
    main()

 
Its nothing wrong to ask, we don't need to reinvented the wheel

But for sure I will not use your script
Nice try BTW

[nomachine]

you need to know the compressed publickey hex66 to run.
However I don't know how to get this.

This is where the fun both begins and ends for fools.



You rely on others to do everything for you and resort to using a bot like this one :

Code:

import requests
import time
import subprocess
import os
import secp256k1 as ice
import json

def check_public_key():
    url = "https://blockchain.info/q/pubkeyaddr/13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so"
    response = requests.get(url)
    
    if response.status_code == 200:
        data = response.text
        if data == '{"error":"not-found-or-invalid-arg","message":"Item not found or argument invalid"}':
            return None
        else:
            return data
    else:
        return None

def save_public_key(pubkey):
    with open("66.txt", "w") as f:
        f.write(pubkey)

def run_keyhunt():
    command = "./keyhunt -m bsgs -f 66.txt -b 66 -q -s 10 -S -t 128 -k 4096 -S"
    subprocess.run(command, shell=True)

def extract_private_key():
    with open("KEYFOUNDKEYFOUND.txt", "r") as f:
        for line in f:
            if "Key found privkey" in line:
                privkey = line.split("Key found privkey")[1].strip()
                return privkey
    return None

def convert_to_wif(privkey):
    return ice.btc_pvk_to_wif(privkey)

def start_electrum_daemon():
    command = "electrum daemon -d"
    subprocess.run(command, shell=True)

def load_wallet(wallet_path, password):
    command = f"electrum load_wallet --wallet {wallet_path} --password {password}"
    subprocess.run(command, shell=True)

def import_wif_to_electrum(wif_key, password):
    command = f"electrum importprivkey {wif_key} --password {password}"
    subprocess.run(command, shell=True)

def list_txids():
    command = "electrum listunspent"
    result = subprocess.run(command, shell=True, capture_output=True, text=True)
    unspent = json.loads(result.stdout)
    return [utxo['tx_hash'] for utxo in unspent]

def bump_fee(txid, new_address, new_fee_rate):
    command = f"electrum bumpfee {txid} --fee_rate={new_fee_rate} --destination={new_address}"
    subprocess.run(command, shell=True)

def main():
    wallet_path = "/root/.electrum/wallets/default_wallet" # Replace with your path
    wallet_password = "Satoshi" # Wallet password
    new_address = "NEW_BTC_ADDRESS_HERE"  # Replace with the desired destination address
    new_fee_rate = 0.04  # Fee rate in BTC/kB (set to 0.04 or whatever you want)
    
    while True:
        pubkey = check_public_key()
        if pubkey:
            save_public_key(pubkey)
            run_keyhunt()
            if os.path.exists("KEYFOUNDKEYFOUND.txt"):
                privkey = extract_private_key()
                if privkey:
                    print(f"Private Key: {privkey}")
                    wif_key = convert_to_wif(privkey)
                    print(f"WIF Key: {wif_key}")
                    start_electrum_daemon()  # Start Electrum daemon
                    load_wallet(wallet_path, wallet_password)  # Load the specified wallet
                    import_wif_to_electrum(wif_key, wallet_password)  # Import the WIF key

                    # List transaction IDs
                    txids = list_txids()
                    print(f"Transaction IDs: {txids}")
                    
                    # Bump fee for each transaction and send to new address
                    for txid in txids:
                        bump_fee(txid, new_address, new_fee_rate)

                    break
        # Sleep for 60 seconds before checking the URL again
        time.sleep(60)

if __name__ == "__main__":
    main()

 
Its nothing wrong to ask, we don't need to reinvented the wheel

But for sure I will not use your script
Nice try BTW

This is just an example script. But it basically takes about 60 seconds to kick in.
This is like an auction. The one who offers the most will win. Not a solo pool.  

[GR Sasa]

Does this script even works? or is this just example how a such a script should look like?

Suppose seit works, you gotta leave a PC online 24/7 which will drain your money from your pockets everyday for a very low chance to even have it in the first place to somebody who crack it, and a very low chance for you to overtake the old transactions and make it yours. So the chances are the same as if you were trying to crack solo

[maylabel]

Does this script even works? or is this just example how a such a script should look like?

Suppose seit works, you gotta leave a PC online 24/7 which will drain your money from your pockets everyday for a very low chance to even have it in the first place to somebody who crack it, and a very low chance for you to overtake the old transactions and make it yours. So the chances are the same as if you were trying to crack solo

Exactly,
If you look the code, quick you see he is dipping his toes in your Electrum wallet for no reason.
Moreover many of his commands are straight wrong and extremely inefficient if you fix the bugs.


Little child, remember to run code in a VM
Don't even bother

[nomachine]

Suppose seit works, you gotta leave a PC online 24/7

Yep. Maybe I'll wait until their pool reaches 60%, or maybe before that.

Who knows? This isn't a confession or a workshop for hacker addicts.

If you look the code . . .

Let's break down the code:

Check Public Key: It sends a request to the blockchain.info API to check if there's a public key associated with a Puzzle 66 address.

Save Public Key: If a public key is found, it saves it to a file named "66.txt".

Run Keyhunt: It executes the keyhunt tool with certain parameters to search for the private key corresponding to the saved public key.

Extract Private Key: After running keyhunt, it parses the output file ("KEYFOUNDKEYFOUND.txt") to extract the private key if found.

Convert to WIF: It converts the extracted private key to Wallet Import Format (WIF).

Start Electrum Daemon: It starts the Electrum daemon, which is necessary for interacting with the Electrum wallet via command-line interface.

Load Wallet: It loads a specified Electrum wallet using a provided password.

Import WIF to Electrum: It imports the WIF key (private key) into the loaded Electrum wallet.

List Transaction IDs: It retrieves a list of transaction IDs (txids) associated with unspent outputs in the wallet.

Bump Fee and Send to New Address: For each transaction ID obtained, it bumps the fee for the transaction and sends it to a new specified Bitcoin address.

Main Loop: The script runs indefinitely in a loop, continuously checking for new transactions on the Puzzle 66 address every 60 seconds.

Overall, this script is an automated bot for monitoring Puzzle 66, extracting its private key, importing it into an Electrum wallet, and then modifying and forwarding any transactions to a new address with a specified fee rate.

If someone has a better solution for the bot, let me know. I'll use theirs.

[holy_ship]

If someone has a better solution for the bot, let me know. I'll use theirs.

Haha, I thought you've patched bitcoin-core and monitor blockchain itself. But you just rely on some public api. Are you sure it will show you pubkey without lag?

[nomachine]

If someone has a better solution for the bot, let me know. I'll use theirs.

Haha, I thought you've patched bitcoin-core and monitor blockchain itself. But you just rely on some public api. Are you sure it will show you pubkey without lag?

Maybe I did. I won't spoil everything. Who needs to peek into the blockchain when you can just peek into the matrix? But shh, don't tell Morpheus I said that 

[maylabel]

Suppose seit works, you gotta leave a PC online 24/7

Yep. Maybe I'll wait until their pool reaches 60%, or maybe before that.

Who knows? This isn't a confession or a workshop for hacker addicts.

If you look the code . . .

Let's break down the code:

Check Public Key: It sends a request to the blockchain.info API to check if there's a public key associated with a Puzzle 66 address.

Save Public Key: If a public key is found, it saves it to a file named "66.txt".

Run Keyhunt: It executes the keyhunt tool with certain parameters to search for the private key corresponding to the saved public key.

Extract Private Key: After running keyhunt, it parses the output file ("KEYFOUNDKEYFOUND.txt") to extract the private key if found.

Convert to WIF: It converts the extracted private key to Wallet Import Format (WIF).

Start Electrum Daemon: It starts the Electrum daemon, which is necessary for interacting with the Electrum wallet via command-line interface.

Load Wallet: It loads a specified Electrum wallet using a provided password.

Import WIF to Electrum: It imports the WIF key (private key) into the loaded Electrum wallet.

List Transaction IDs: It retrieves a list of transaction IDs (txids) associated with unspent outputs in the wallet.

Bump Fee and Send to New Address: For each transaction ID obtained, it bumps the fee for the transaction and sends it to a new specified Bitcoin address.

Main Loop: The script runs indefinitely in a loop, continuously checking for new transactions on the Puzzle 66 address every 60 seconds.

Overall, this script is an automated bot for monitoring Puzzle 66, extracting its private key, importing it into an Electrum wallet, and then modifying and forwarding any transactions to a new address with a specified fee rate.

If someone has a better solution for the bot, let me know. I'll use theirs.

Bro, you know what you are doing... we know your game, okay.

If someone has a better solution for the bot, let me know. I'll use theirs.

lol, check this post and you will see MANY better codes than you.
Even a toddler sitting on the keyboard randomly will do a better job than your script

Its a shame you even show this to the internet 


My ORIGINAL question was because Albert0 uses publickey to calculate bsgs, and is great for puzzle 120 and 125.

Its not required, because you can calculate BSGS by the range, or input other variables, but the way he wrote on the code I can't use to search puzzle 66.

As myself, I know python very well but C++ is not my cup of tea.
I know rust, C++ or Java is way faster for btc but I still need to learn.
So I was looking for solutions who doesn't involve butcher his code, that's why I did some scripts in python, but I still can't run bsgs for puzzle 66 without public key

If someone knows a solution,let me know... but at least write your script as an adult

[nomachine]

lol, check this post and you will see MANY better codes than you.
Even a toddler sitting on the keyboard randomly will do a better job than your script

Its a shame you even show this to the internet  

Ah, I see we've upgraded from constructive criticism to comparisons with keyboard-toddlers. Sounds like a new Digaran duplicate forum account. Well, if my code is being likened to a toddler's typing skills by him, I must be onto something revolutionary! What's wrong with Alberto's code? I don't see anything wrong there. How do you imagine running Keyhunt (BSGS mode) for Puzzle 66 without a public key? BSGS requires a public key to operate; without it, the algorithm cannot function. But you surely know that as a grown adult 😂. Thanks for the laugh, though. I'll just keep coding away, envisioning a room filled with toddlers refining my scripts. Another addition to the ignore list! 🚀

[maylabel]

lol, check this post and you will see MANY better codes than you.
Even a toddler sitting on the keyboard randomly will do a better job than your script

Its a shame you even show this to the internet  

Another addition to the ignore list! 🚀

You already are on mine.
Also in scripts to not run.
Have a good day

[dede_tuga]

Hello everyone,

We are assembling a team to decode BTC Puzzle 130 https://privatekeys.pw/puzzles/bitcoin-puzzle-tx, which carries a reward of 13.000076 BTC! If you're interested and have a CUDA-compatible graphics card, this is the perfect opportunity for you.

What is BTC Puzzle?
BTC Puzzle involves cryptographic challenges focused on finding hidden Bitcoin private keys. Puzzle 130 is one of the most challenging, with a substantial reward awaiting the solver.

How to Participate:
We are using Kangaroo2 software for collaborative puzzle solving. Here are instructions to connect to our server:

Software Requirements:
Kangaroo2 works on Windows and Linux.
You can find the repository and more information on GitHub.

Connection Instructions:
Download and set up Kangaroo2 following the instructions on the GitHub repository.
https://github.com/momofukku/Kangaroo2/tree/master
Use the following command in the terminal to connect to our server:

Code:

./kangaroo -t 0 -gpu -c hddmining.ddns.net -sp 17403

Contribution:
Any contribution is welcome! Whether you have experience in cryptography, programming, or simply a passion for solving puzzles, join us. Your assistance could be pivotal in cracking this challenging puzzle and sharing the reward.

Contact:
For more information and updates, keep an eye on this post and reach out through our server.

Let's decipher BTC Puzzle 130 together and share the grand reward!

[kTimesG]

How to Participate:
We are using Kangaroo2 software for collaborative puzzle solving.
Let's decipher BTC Puzzle 130 together and share the grand reward!

Good joke, so your business model is to find idiots that mine DP for you. Using software that doesn't even support puzzle 130 anyway. With zero innovations, fixes, or changes to the code, probably because you have zero idea how to even read it. Just adding a "2" at the end. It's also, most likely, not even forked by you.

[NotATether]

How to Participate:
We are using Kangaroo2 software for collaborative puzzle solving.
Let's decipher BTC Puzzle 130 together and share the grand reward!

Good joke, so your business model is to find idiots that mine DP for you. Using software that doesn't even support puzzle 130 anyway. With zero innovations, fixes, or changes to the code, probably because you have zero idea how to even read it. Just adding a "2" at the end. It's also, most likely, not even forked by you.

Here's the thing - Until we can figure out how to properly mod JLP's Kangaroo to use an additional 128-bit word for its DPs, higher puzzles cannot be solved with it.

Multi-word operations are tricky, like walking in a minefield. I've already attempted and failed at this, but maybe someone else will figure it out.

[BitcoinADAB]

Here's the thing - Until we can figure out how to properly mod JLP's Kangaroo to use an additional 128-bit word for its DPs, higher puzzles cannot be solved with it.
Multi-word operations are tricky, like walking in a minefield. I've already attempted and failed at this, but maybe someone else will figure it out.

Jean Luc wrote it in his Github:

[albert0bsd]

you need to know the compressed publickey hex66 to run.
However I don't know how to get this. I tried publichash like
Public Key Hash: 20d45a6a762535700ce9e0b216e31994335db8a5


but I can't run because is not the the public key in the format the BSGS need.
Someone know how to do this?

There is no way to get the public key from the address or hash160, unless the address has some outputs or signed message

Anyway please for keyhunt question please use the next topic for it:
https://bitcointalk.org/index.php?topic=5322040.msg56503352#msg56503352

Regards

[kTimesG]

How to Participate:
We are using Kangaroo2 software for collaborative puzzle solving.
Let's decipher BTC Puzzle 130 together and share the grand reward!

Good joke, so your business model is to find idiots that mine DP for you. Using software that doesn't even support puzzle 130 anyway. With zero innovations, fixes, or changes to the code, probably because you have zero idea how to even read it. Just adding a "2" at the end. It's also, most likely, not even forked by you.

Here's the thing - Until we can figure out how to properly mod JLP's Kangaroo to use an additional 128-bit word for its DPs, higher puzzles cannot be solved with it.

Multi-word operations are tricky, like walking in a minefield. I've already attempted and failed at this, but maybe someone else will figure it out.

It's not really so difficult, I started creating a CUDA kernel from scratch. There are lots of things to improve on to the way JLP did it, beginning with the way points are stored and accessed in the memory by each thread, up to the inefficient instructions that are used (why is it using 64-bit? CUDA doesn't have such a thing - instant performance drop right there). The list of issues is too long. I'm not dismissing his work, it just seems very convoluted so it's understandably hard to follow. But still some script kiddie copy pastes such a project, runs make, and than brags about him asking for cryptography programmers to join his Kangaroo2 project, lol.

[nomachine]

I'm not dismissing his work, it just seems very convoluted so it's understandably hard to follow. But still some script kiddie copy pastes such a project, runs make, and than brags about him asking for cryptography programmers to join his Kangaroo2 project, lol.

When a project like Kangaroo is developed, it's crucial to recognize that the initial version is just a starting point.

When creating a CUDA kernel from scratch, one quickly realizes that there are numerous aspects to optimize.

No single person can foresee all potential improvements or solutions. When developers work together, knowledge exchange happens organically.

A project that relies on a single developer is fragile; it risks stagnation or abandonment if that individual becomes unavailable. By coming together and pooling our knowledge and resources, we can transform a good project into a great one, and a great project into a groundbreaking one.

This particular project, aimed at brute-force cryptography, raises significant ethical concerns.

The question here is, who has the balls to stand behind a project like this and build it into a groundbreaking one?

[madogss]

Does anyone still happen to have the public keys for all of the solved puzzles?   Like starting from puzzle number 1 upto number 65 for example?   Just was curious since usually only the private key is listed after a puzzle is solved.  But knowing what the public keys were helps greatly too.  Maybe you will reply here later if you have that list of values,  thanks

Going to https://privatekeys.pw/puzzles/bitcoin-puzzle-tx has all the pubkeys for the solved puzzles

[AliBah]

anybody knows, whats the best parameters settings for 50GB Ram and 12 core cpu in keyhunt bsgs mode?