Bitcoin puzzle transaction ~32 BTC prize to who solves it

[AliBah]

What if someone found the key and spent the btc to another wallet ( i know, pubkey...) but with a super high tx fee, like extremely high.

Which key? puzzle key? 66?

If the 66 key is spent it may enter in some bot fight each one will increase the fees compared to other until there is nothing left to spent but the final result is unknown

Not always the higher fee wins, chek my previous reply to this:

Just to mention that when the nodes have many FullRBF transacions not always win that one with more fee, here some examples, Dot with Green margin was mined, some are Testnet and other are mainnet


https://talkimg.com/images/2024/03/19/JJJn9.png
Here was mined a TX with 1 sat/vB instead of a 37 sat/vB

https://talkimg.com/images/2024/03/19/JJVvN.png
Here was mined a TX with 22 sat/vB instead of a 44 sat/vB

https://talkimg.com/images/2024/03/19/JJjia.png
Here was mined a TX with 106 sat/vB instead of a 1032 sat/vB

All depens of what is the transaction that the miner selected to work with his hardware.

I tried to import a private key into bitcoin core but i got this error :



Only legacy wallets are supported by this command (code -4)

what should i do now?

If you don't show what command do you used, then there is no way to know what is wrong.

What kind of address are you trying to import? it looks like it is not a legacy one.

I tried to test this:
HEX fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364140
WIF(c) L5oLkpV3aqBjhki6LmvChTCV6odsp4SXM6FfU2Gppt5kFLaHLuZ9
WIF(u) 5Km2kuu7vtFDPpxywn4u3NLpbr5jKpTB3jsuDU2KYEqetqj84qw

by this command  : importprivkey


Finally i found how to import wallets, but whats this error now... errors killing me haha



importdescriptors "[{\"desc\": \"wpkh(L5oLkpV3aqBjhki6LmvChTCV6odsp4SXM6FfU2Gppt5kFLaHLuZ9)#c9eja2dd\", \"timestamp\": 0}]"



[
  {
    "success": false,
    "error": {
      "code": -1,
      "message": "Rescan failed for descriptor with timestamp 0. There was an error reading a block from time 1711177032, which is after or within 7200 seconds of key creation, and could contain transactions pertaining to the desc. As a result, transactions and coins using this desc may not appear in the wallet. This error could be caused by pruning or data corruption (see bitcoind log for details) and could be dealt with by downloading and rescanning the relevant blocks (see -reindex option and rescanblockchain RPC)."
    }
  }
]

[1715368355]

1715368355

[mkd097]

What program supports bulk HEX range list for scanning Bitcoin addresses?

[jacky19790729]

Code:

Address = 13zb1hQbWVuYdZoAkztVrNrm65aReL2pYD
Message = I own this address
Signature = HxSDzJj3BhS8lh7qoU1L9zJsymorFkJv8/roi8o6+269PEDPr8psAE1QEOerWAWKv/ypXss7hhXEe0FutUR4b0s=

your address:  13zb1hQbWVuYdZoAkztVrNrm65aReL2pYD  
public key:    03f3fb41f466d9893e5af7dfd788211b0503eb38d49615a19aa22b419ed4ff308d
private key:   0x2CA8A08241FC8D6EF


   
 10 char match #66

Code:

I tried to test this: 
HEX fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364140 
WIF(c) L5oLkpV3aqBjhki6LmvChTCV6odsp4SXM6FfU2Gppt5kFLaHLuZ9 
WIF(u) 5Km2kuu7vtFDPpxywn4u3NLpbr5jKpTB3jsuDU2KYEqetqj84qw 

by this command  : importprivkey 

importprivkey L5oLkpV3aqBjhki6LmvChTCV6odsp4SXM6FfU2Gppt5kFLaHLuZ9 "" false

[albert0bsd]

your address:  13zb1hQbWVuYdZoAkztVrNrm65aReL2pYD  

Try to quote from the person who post it in first place.

Good that you also found the key, but you spoil it. You just removed the fun for others. It would be better another signed message no?

Quoting to the user who post it:

Address = 13zb1hQbWVuYdZoAkztVrNrm65aReL2pYD
Message = I own this address
Signature = HxSDzJj3BhS8lh7qoU1L9zJsymorFkJv8/roi8o6+269PEDPr8psAE1QEOerWAWKv/ypXss7hhXEe0FutUR4b0s=

[hellishgoblin234]

Not always the higher fee wins, chek my previous reply to this:

Thank you, very interesting.

Yes, regarding puzzle #66. So, what would be the safest way to spend the coins to another wallet then?

I mean, what is even the point of spending time & resources on finding the privkey if it is then impossible to spend the coins (or at least most of them) to another wallet safely because an army of monitoring agents will attempt to steal the coins by cracking the privkey using kangoroo with the newly avail. pubkey.

[AndrewWeb]

Thank you, very interesting.

Yes, regarding puzzle #66. So, what would be the safest way to spend the coins to another wallet then?

I mean, what is even the point of spending time & resources on finding the privkey if it is then impossible to spend the coins (or at least most of them) to another wallet safely because an army of monitoring agents will attempt to steal the coins by cracking the privkey using kangoroo with the newly avail. pubkey.

Solve a Bitcoin block, then include your transaction within the block you solved.

If you're not a Bitcoin miner, find a Bitcoin miner to do it for you.

[brainless]

Thank you, very interesting.

Yes, regarding puzzle #66. So, what would be the safest way to spend the coins to another wallet then?

I mean, what is even the point of spending time & resources on finding the privkey if it is then impossible to spend the coins (or at least most of them) to another wallet safely because an army of monitoring agents will attempt to steal the coins by cracking the privkey using kangoroo with the newly avail. pubkey.

Solve a Bitcoin block, then include your transaction within the block you solved.

If you're not a Bitcoin miner, find a Bitcoin miner to do it for you.

Or you can share coins with me for safe tx

[Feron]

when someone solves it, they just take it, no stress

[satashi_nokamato]

Finally i found how to import wallets, but whats this error now... errors killing me haha



importdescriptors "[{\"desc\": \"wpkh(L5oLkpV3aqBjhki6LmvChTCV6odsp4SXM6FfU2Gppt5kFLaHLuZ9)#c9eja2dd\", \"timestamp\": 0}]"



[
  {
    "success": false,
    "error": {
      "code": -1,
      "message": "Rescan failed for descriptor with timestamp 0. There was an error reading a block from time 1711177032, which is after or within 7200 seconds of key creation, and could contain transactions pertaining to the desc. As a result, transactions and coins using this desc may not appear in the wallet. This error could be caused by pruning or data corruption (see bitcoind log for details) and could be dealt with by downloading and rescanning the relevant blocks (see -reindex option and rescanblockchain RPC)."
    }
  }
]

I believe Bitcoin core client refuses to import 1 and -1 keys, so you can't import those 2 keys.

[zahid888]

Code:

from cryptography.fernet import Fernet
from cryptography.hazmat.backends import default_backend
from cryptography.hazmat.primitives import hashes
from cryptography.hazmat.primitives.kdf.pbkdf2 import PBKDF2HMAC
import base64
import os
import getpass

# Function to generate a key from the password
def key_from_password(password, salt):
    kdf = PBKDF2HMAC(
        algorithm=hashes.SHA256(),
        length=32,
        salt=salt,
        iterations=100000,
        backend=default_backend()
    )
    key = base64.urlsafe_b64encode(kdf.derive(password.encode()))
    return key

# Encrypt the message
def encrypt_message(message, password):
    salt = os.urandom(16)
    key = key_from_password(password, salt)
    fernet = Fernet(key)
    encrypted = fernet.encrypt(message.encode())
    return encrypted, salt

# Decrypt the message
def decrypt_message(encrypted_message, password, salt):
    key = key_from_password(password, salt)
    fernet = Fernet(key)
    try:
        decrypted = fernet.decrypt(encrypted_message).decode()
        return decrypted
    except Exception as e:
        return "Error: " + str(e)

# Main interface
if __name__ == "__main__":
    choice = input("Do you want to encrypt or decrypt a message? (encrypt/decrypt): ")
    
    if choice == "encrypt":
        secret_message = input("Enter your secret message: ")
        password = getpass.getpass("Enter a password for encryption: ")
        encrypted_message, salt = encrypt_message(secret_message, password)
        print("Your encrypted message is:")
        print(encrypted_message.decode())
        print("Your salt (needed for decryption) is:")
        print(base64.b64encode(salt).decode())
    elif choice == "decrypt":
        encrypted_message_input = input("Enter the encrypted message: ")
        salt_input = base64.b64decode(input("Enter the salt: "))
        password = getpass.getpass("Enter the password for decryption: ")
        decrypted_message = decrypt_message(encrypted_message_input.encode(), password, salt_input)
        print("Your decrypted message is:")
        print(decrypted_message)
    else:
        print("Invalid choice. Please type 'encrypt' or 'decrypt'.")

Example:

Encrypted message is: gAAAAABmCsIhWZe1vm94Ma4p6v3hv8LmP5JuvhsA1qI65TK_X2LolyNqEFr2y2yZyORoi5KuVubjyay nScTIfAKrqBka17jslzoHfVTB7-c1fgx-qjbjTbDEDUG5vlCE0qy5uOgqBYG4jt5b9gxnhBdVLL3qc2e7nw==-c1fgx-qjbjTbDEDUG5vlCE0qy5uOgqBYG4jt5b9gxnhBdVLL3qc2e7nw==

Salt (needed for decryption) is: IJZVtFg2B1u5r/A1bsk/TA==

The password for decryption is: password
Whoever manages to obtain the private key for Puzzle 66.
Is requested to encrypt it using this script and post the encrypted message here. Post only the encrypted message, and keep the salt and password to yourself.
Then, proceed to complete your transaction process after few days. If, for any reason, the transaction fails to validate and someone else hijacks it,
You are encouraged to post your salt and password here as evidence that you had solved Puzzle 66.
This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.
@alberto or any other member, if you discover any vulnerabilities here or are capable of cracking this script, please inform us. Additionally, if there are any alternative implementations, kindly share those as well.

[citb0in]

Whoever manages to obtain the private key for Puzzle 66. Is requested to encrypt it using this script and post the encrypted message here. ---snip---

there is absolutely no reason why the person should obey your orders.

This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.

there are no "legal actions", you joker. If someone has the private key to a Bitcoin address, they can unlock using script and access the contents of the vault. Whether you like it or not. Wake up

@alberto or any other member, if you discover any vulnerabilities here or are capable of cracking this script, please inform us. Additionally, if there are any alternative implementations, kindly share those as well.

Are you the self-appointed Bitcoin Sheriff or his deputy?

... Oh sorry, now I understand. That was an April Fool's joke. No offense, it was a good one

[zahid888]

This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.

Wake up

Hey, you well-dwelling toad, wake up a bit. A Bitcoin address isn't entirely anonymous. At the very least, we can demand some percentage from that person.

Oh sorry, now I understand. That was an April Fool's joke. No offense, it was a good one

Upon reviewing his many posts, It's evident that he has nothing to do besides poking his nose into others' business. He hasn't shared any ideas or help for the community so far, except for poking others.This person demonstrates a highly negative and narrow-minded attitude. I'm fully confident that he hasn't spent a single penny to solve this puzzle, but if he gets something for free, he's ready to grab it like a dog.

If he had worked hard and invested money, he would have been worried about not wasting his effort . He would be concerned about ensuring that their efforts and funds are not wasted and would seek ways to avoid such wastage. Whether it works or not, This post is intended for those who have invested significantly here. For you, this may indeed be considered a joke but not for all. Kindly refrain from nonsense talk and let the community members decide whether this method is appropriate or not. After all, I am not imposing it on them.

[JonJonBon]

Im using this command :
.\keyhunt.exe -m bsgs -f keys.txt -b 130 -t 4 -s 10 -k 256 -S
should i change something or this is my power and i cant do anything more ?

Hi albert0bsd, could you leave me your email in a private message, I have an idea for your keyhunt program, business suggestions!.
Your problem is the .exe and windows stuff

Don use it on windows, compile it your self in a WSL environment or native linux

The lastest version is Version 0.2.230519 Satoshi Quest it provide an increment of speed X2 compared with previous version

[jacky19790729]

Whoever manages to obtain the private key for Puzzle 66.
Is requested to encrypt it using this script and post the encrypted message here. Post only the encrypted message, and keep the salt and password to yourself.
Then, proceed to complete your transaction process after few days. If, for any reason, the transaction fails to validate and someone else hijacks it,
You are encouraged to post your salt and password here as evidence that you had solved Puzzle 66.
This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.
@alberto or any other member, if you discover any vulnerabilities here or are capable of cracking this script, please inform us. Additionally, if there are any alternative implementations, kindly share those as well.

Just the first person who solves Puzzle 66 issues the first 32 bytes + 32 bytes of the public key and replaces it with ***********
example:   023b1ac48deb1302bbc9bd302104e6747**************************
The first person who solves Puzzle 66  can post it in this thread or a YouTube video... record the time

It can prove that he is the first person to discover the private key of Puzzle 66... ​​and transfer 6.6 BTC away the next day...
But of course thousands of programs will leak the public key within 1 minute after the transaction, and snatch this bonus
No one Really legal possession....
Even the creator saatoshi_rising cannot sue because he has already released the BTC ...as game bonuses

[mckemo]

What if someone found the key and spent the btc to another wallet ( i know, pubkey...) but with a super high tx fee, like extremely high.

Which key? puzzle key? 66?

If the 66 key is spent it may enter in some bot fight each one will increase the fees compared to other until there is nothing left to spent but the final result is unknown

Not always the higher fee wins, chek my previous reply to this:

Just to mention that when the nodes have many FullRBF transacions not always win that one with more fee, here some examples, Dot with Green margin was mined, some are Testnet and other are mainnet


https://talkimg.com/images/2024/03/19/JJJn9.png
Here was mined a TX with 1 sat/vB instead of a 37 sat/vB

https://talkimg.com/images/2024/03/19/JJVvN.png
Here was mined a TX with 22 sat/vB instead of a 44 sat/vB

https://talkimg.com/images/2024/03/19/JJjia.png
Here was mined a TX with 106 sat/vB instead of a 1032 sat/vB

All depens of what is the transaction that the miner selected to work with his hardware.

I tried to import a private key into bitcoin core but i got this error :



Only legacy wallets are supported by this command (code -4)

what should i do now?

If you don't show what command do you used, then there is no way to know what is wrong.

What kind of address are you trying to import? it looks like it is not a legacy one.

Wow, i just learned that this features exists. so  even having the key for 66, you are not safe because of bots just waiting  to get a signal from the network and getting the privkey within seconds via bsgs /kangaroo.

blocktime is 10 mins - do you think it is possible, that you e.g. wait 9 mins, set the reward extremly high (like 0.09 btc) and distribute it ?

[citb0in]

blocktime is 10 mins - do you think it is possible, that you e.g. wait 9 mins, set the reward extremly high (like 0.09 btc) and distribute it ?

The 10 minutes is the average time. There are enough cases in which no block has fallen for almost an hour and other cases in which several blocks have fallen within a minute. So there is no guarantee that you will send the transaction to the net just before 10 minutes have elapsed and the next block will fall shortly afterwards. That would be a huge amount of luck that you would also need. The only way out of this dilemma, as already mentioned several times, is to find a large miner who will include your transaction in the next block to be calculated. This large miner must have so much power that he regularly mines blocks and the probability is in your favor that he will ever mine a block. And of course there must be an incentive for this miner, perhaps in the form of a reasonable commission, to comply with your request and make the extra effort to do so. Very unlikely, but not impossible.

All other dubious and questionable methods mentioned here are not target-oriented but misleading and inspire false confidence, just like the last hopeless appeal of a desperate user. Even if you were to find out the key and provide some form of proof here in the forum that you know the key, it would not change the fact that you have no legal right to open the vault and obtain the contents. To make this clear, let's take a simple example: imagine that Alice has known the key from #66 for over a year. This fact alone does not make her the owner of the contents of the safe from puzzle #66. If Mallory finds out the key 3 years later and grabs the coins from #66, they belong to Mallory. That's the way the game is, that's how it's defined in Bitcoin and there is no "law" or "rules". The mighty power is written in Bitcoin protocol and everything is defined in there.

[mckemo]

blocktime is 10 mins - do you think it is possible, that you e.g. wait 9 mins, set the reward extremly high (like 0.09 btc) and distribute it ?

The 10 minutes is the average time. There are enough cases in which no block has fallen for almost an hour and other cases in which several blocks have fallen within a minute. So there is no guarantee that you will send the transaction to the net just before 10 minutes have elapsed and the next block will fall shortly afterwards. That would be a huge amount of luck that you would also need. The only way out of this dilemma, as already mentioned several times, is to find a large miner who will include your transaction in the next block to be calculated. This large miner must have so much power that he regularly mines blocks and the probability is in your favor that he will ever mine a block. And of course there must be an incentive for this miner, perhaps in the form of a reasonable commission, to comply with your request and make the extra effort to do so. Very unlikely, but not impossible.

All other dubious and questionable methods mentioned here are not target-oriented but misleading and inspire false confidence, just like the last hopeless appeal of a desperate user. Even if you were to find out the key and provide some form of proof here in the forum that you know the key, it would not change the fact that you have no legal right to open the vault and obtain the contents. To make this clear, let's take a simple example: imagine that Alice has known the key from #66 for over a year. This fact alone does not make her the owner of the contents of the safe from puzzle #66. If Mallory finds out the key 3 years later and grabs the coins from #66, they belong to Mallory. That's the way the game is, that's how it's defined in Bitcoin and there is no "law" or "rules". The mighty power is written in Bitcoin protocol and everything is defined in there.

thank you. this feature is really fucked up .
like there is no max or smth.  or a security. they should have integrated, that coins are locked in some way as long as the transaction is ongoing and that you can not change the destination address.

[citb0in]

thank you. this feature is really fucked up .
like there is no max or smth.  or a security. they should have integrated, that coins are locked in some way as long as the transaction is ongoing and that you can not change the destination address.

you come to this conclusion solely from the perspective of your current glasses in the position of puzzle hunter #66. otherwise, RBF and similar techniques have their reason of existence and this was also agreed with the developers and thus implemented. But that would be totally off-topic now, if you want to read more about it, you will find plenty of information in the corresponding sections here in the forum.

I agree with you that this is a pretty stupid circumstance. This is also due to the fact that we now have tools like BSGS and Kangaroo that can calculate the private key very quickly if the public key and the corresponding range are known. Unfortunately, this is suboptimal for us puzzle hunters

[zahid888]

Whoever manages to obtain the private key for Puzzle 66.
Is requested to encrypt it using this script and post the encrypted message here. Post only the encrypted message, and keep the salt and password to yourself.
Then, proceed to complete your transaction process after few days. If, for any reason, the transaction fails to validate and someone else hijacks it,
You are encouraged to post your salt and password here as evidence that you had solved Puzzle 66.
This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.
@alberto or any other member, if you discover any vulnerabilities here or are capable of cracking this script, please inform us. Additionally, if there are any alternative implementations, kindly share those as well.

Just the first person who solves Puzzle 66 issues the first 32 bytes + 32 bytes of the public key and replaces it with ***********
example:   023b1ac48deb1302bbc9bd302104e6747**************************
The first person who solves Puzzle 66  can post it in this thread or a YouTube video... record the time

It can prove that he is the first person to discover the private key of Puzzle 66... ​​and transfer 6.6 BTC away the next day...
But of course thousands of programs will leak the public key within 1 minute after the transaction, and snatch this bonus
No one Really legal possession....
Even the creator saatoshi_rising cannot sue because he has already released the BTC ...as game bonuses

This is also a good idea, but when you publicly post either the beginning or the end part of the 32-bit public key of puzzle 66, I am completely sure that Satoshi himself will sweep puzzle 66 .. just like he has done with puzzle 120 and puzzle 125.. and he has not even spent those coins yet, which proves that he has done it,, but if we post a lot of encrypted messages in which fake and real are mixed,, then Satoshi will not even know, and after the public key is exposed, it will be known who has posted the real key.
Whether someone does it or not, I am definitely going to do it. I have scanned 12% so far, but if luck doesn't support us, what can we do? I am telling everyone to do this because I am very curious to see this process, and conducting this process silently would only perpetuate confusion surrounding the issue forever.

[kTimesG]

You are encouraged to post your salt and password here as evidence that you had solved Puzzle 66.
This will enable the entire community to potentially pursue legal action against the thief. Therefore, anyone attempting to undermine someone else's hard work is hereby warned.
@alberto or any other member, if you discover any vulnerabilities here or are capable of cracking this script, please inform us. Additionally, if there are any alternative implementations, kindly share those as well.

Why not simply AES-256 encrypt the private key and be done with it in, like, 3 lines? No password hashing and so on.

I solved puzzle #66 but I'm very afraid to sweep it. Since no one claimed it yet, they definitely belong to me, right? Here's my proof: the encrypted private key is:

Code:

0x4074a46512e55c9559cb8af86c983bc424d9f2d5fbb3c14b65b1045d21972d219b359a24806826a94c72e9a95ca00dab

First 16 bytes are the IV, then 32 bytes of private key. I removed the padding, since it's 16 bytes of 0x10 (e.g. no bytes in last block).

If anyone steals my prize I will divulge the decryption key.

Or, simply hash it once together with some secret value, you only need to prove you knew the hashed value before anyone else, not to protect the actual data.

Code:

SHA256(privateKey + "some secret value")