Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
zahid888
on 25/12/2023, 09:18:36 UTC
Take your chances by deploying a bot to compete with the looter, otherwise you can kiss your coins good bye. Or just talk  with a large pool beforehand, you could offer them $10,000 bonus and if they include the tx in their block, other pools won't dare to mine that block again just to take those extra coins.

So you are claiming that any Bitcoin transaction could be double-spended and therefore all Bitcoin transactions are insecure. Makes sense ?

What do you think of a challenge? I transfer an amount of x coins, you only know the source address, which I will publish here. Its private key will be in the range of 66bit just like the mentioned puzzle. Then you siphon off the coins and transfer them to another address before I receive them just like you described the looter would. If the coins end up at your freely chosen address, you can keep them. If they end up with me, you have lost and made a fool of yourself. Deal ?

He is speaking quite accurately. I have witnessed numerous instances where some private keys which have been compromised. Many individuals have set up auto-send bots with those compromised keys. If any funds accidentally land there, they are immediately transferred, and it waits for confirmation. Suddenly, a miner arrives and brings 1 confirmation with him. Before the individuals transaction is confirmed, it conflicts with the 1 confirmation, and the funds are transferred to the miner who broadcasts the tx_hash with The hellll Angry Angry 1 confirmation with his pocket Shocked. I watch such cases about 4 or 5 times in a month. 1 ex: below



I urge Satoshi Nakamoto to promptly close this loophole. Only then will it be enjoyable to take on the challenge of this puzzle. Otherwise, it would be better for all of us to gracefully withdraw from this challenge. The one who has the private key and has signed the first transaction with sufficient fees, until that transaction is confirmed, no other tx_hash related to that address should be submitted in the mempool. Implementing this much is not a difficult task.