Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Kamoheapohea]

I will join and create my transaction with 6.6 BTC fees 

[BackyardGeniusBTC]

Hey, i have somethings id like to chat about in regards to addressmagic. no im not a troll <3 but i think we could benefit from each other.

I WILL NOT ASK YOU FOR CRYPTO OR MONEY I AM PURELY A NERD

Hey, i have somethings id like to chat about in regards to addressmagic. no im not a troll <3 but i think we could benefit from each other.

I WILL NOT ASK YOU FOR CRYPTO OR MONEY I AM PURELY A NERD

P.S THIS IS MY FIRST BTCTALK account i have no idea how to navigate it lol

[GR Sasa]

@nomachine

could you please give us a step by step tutorial to run a script to try to drain the bitcoin?

Since it's in 4 hours and since he's doing it live, I would probably try to manually extract the public key and manually try to re send the transaction. But since there are million of transaction how to catch the targeted address?

[albert0bsd]

But since there are million of transaction how to catch the targeted address?

I use the mempool API in my script/bot
https://mempool.space/docs/api/rest#get-address-transactions-mempool

you can retrieve the mempool TX related to one address even if those TX are unconfirmed

Code:

curl -sSL "https://mempool.space/api/address/197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ/txs/mempool"

[nomachine]

@nomachine

could you please give us a step by step tutorial to run a script to try to drain the bitcoin?

Since it's in 4 hours and since he's doing it live, I would probably try to manually extract the public key and manually try to re send the transaction. But since there are million of transaction how to catch the targeted address?

Here’s how you can do it in Python:

Code:

pip3 install requests

one-line command in Python

1DWQHdi1mh27vcUyrN5NYB1kWrs3BBKUXA :

Code:

python3 -c "import requests; import sys; address = sys.argv[1]; url = f'https://mempool.space/api/address/{address}/txs/chain'; r = requests.get(url); txs = r.json(); pubkey = next((vin['scriptsig'][-66:] for tx in txs for vin in tx['vin'] if 'scriptsig' in vin), None); print(f'Public key for address {address}: {pubkey}' if pubkey else 'Public key not found');" 1DWQHdi1mh27vcUyrN5NYB1kWrs3BBKUXA

197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ :

Code:

python3 -c "import requests; import sys; address = sys.argv[1]; url = f'https://mempool.space/api/address/{address}/txs/chain'; r = requests.get(url); txs = r.json(); pubkey = next((vin['scriptsig'][-66:] for tx in txs for vin in tx['vin'] if 'scriptsig' in vin), None); print(f'Public key for address {address}: {pubkey}' if pubkey else 'Public key not found');" 197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ

All you need to do is press Enter until it appears. It will appear the moment he clicks send.

[kTimesG]

Let's hope that n00b bots won't increase the fee when they detect their own tx in the mempool during the battle.

[wilspen]

Let's hope that n00b bots won't increase the fee when they detect their own tx in the mempool during the battle.

fierce battle in the mempool in the wallet    
197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ with RBF disabled

It was already supposed to be 66, it's been proven that even with RBF deactivated and it's possible to change, there were more than 4 RBF from what I saw

[GR Sasa]

fucking hell, i couldn't replace the transaction by any higher fee i got the error saying insufficient fees. wtf

[averagetoaster]

Barely caught it myself. I guess this confirms that anything under 90 or 100 is a waste of time.
Thank you for the experiment, brazilian man.

[wilspen]

fucking hell, i couldn't replace the transaction by any higher fee i got the error saying insufficient fees. wtf

In this case they did not use a wallet, a direct process was carried out in the transaction, AlbertoBSD won the battle, and could give us more details of what was done.     

[kTimesG]

fucking hell, i couldn't replace the transaction by any higher fee i got the error saying insufficient fees. wtf

Weird. All I got was "Error: txn-mempool-conflict" when trying to push the new TX (key was cracked in seconds).

So I guess it depends on how to push a raw TX bypassing this error. I'm sure a P2P node can bypass this problem. So not sure what exactly was proven here, except some mempool rules depending on who you broadcast the TX to.

[GR Sasa]

Congrats if Alberto Won. Clearly he deserved it, along with Nomachine Wanderingidkphotopsia too

[WanderingPhilospher]

Can anyone give a rundown on what happened?

Like the original broadcasted transaction, the competing transactions, and which one won?

[wilspen]

fucking hell, i couldn't replace the transaction by any higher fee i got the error saying insufficient fees. wtf

Weird. All I got was "Error: txn-mempool-conflict" when trying to push the new TX (key was cracked in seconds).

So I guess it depends on how to push a raw TX bypassing this error. I'm sure a P2P node can bypass this problem. So not sure what exactly was proven here, except some mempool rules depending on who you broadcast the TX to.

Is it not clear what was proven? hears at least 4 RBF in the transaction, and the transaction was sent with the RBF deactivated, finally, to the guy who said he found wallet 66 and is scared, it's proven that he will lose the BTCs if he tries to transfer, and to the rest of the people who are looking for it, it is worth reflecting on whether it is worth wasting energy looking for a key when they could lose the funds, perhaps the only way to make the transfer securely is through a miner, but even then it would be risky, you have to trust too much in the miner, hahaha

[kTimesG]

fucking hell, i couldn't replace the transaction by any higher fee i got the error saying insufficient fees. wtf

Weird. All I got was "Error: txn-mempool-conflict" when trying to push the new TX (key was cracked in seconds).

So I guess it depends on how to push a raw TX bypassing this error. I'm sure a P2P node can bypass this problem. So not sure what exactly was proven here, except some mempool rules depending on who you broadcast the TX to.

Is it not clear what was proven? hears at least 4 RBF in the transaction, and the transaction was sent with the RBF deactivated, finally, to the guy who said he found wallet 66 and is scared, it's proven that he will lose the BTCs if he tries to transfer, and to the rest of the people who are looking for it, it is worth reflecting on whether it is worth wasting energy looking for a key when they could lose the funds, perhaps the only way to make the transfer securely is through a miner, but even then it would be risky, you have to trust too much in the miner, hahaha

I have no idea what actually went down, I didn't understand anything from the live stream. All I know was I tried pushing around 20 or so transactions with higher fees (no RBF, classic TX) and none went through due to "mempool rules" errors. I searched for different broadcasters to push the raw TX (even chinese lol). I am 100% sure there had to exist a way to push a completely valid TX with a higher fee.

Also did the mempool.space API worked? Maybe I had an error in my script but it didn't seem to return any data for the outgoing transaction which was supposed to be used as an input, during all of the time. Someone can shed light if their API worked or not?

[wilspen]

Can anyone give a rundown on what happened?

Like the original broadcasted transaction, the competing transactions, and which one won?

Take a look at the previous posts and you will understand the context.

[lmajowka]

Barely caught it myself. I guess this confirms that anything under 90 or 100 is a waste of time.
Thank you for the experiment, brazilian man.

Thank you to everyone that participated 🙏

[WanderingPhilospher]

Can anyone give a rundown on what happened?

Like the original broadcasted transaction, the competing transactions, and which one won?

Take a look at the previous posts and you will understand the context.

Yeah, Bud, I know the concept of this whole test. I wanted to know if anyone took snapshots or notes, of how many different people / competing transactions were happening, before whichever one, finally got through. The play by play, wilspen.

[jacky19790729]

Can anyone give a rundown on what happened?
Like the original broadcasted transaction, the competing transactions, and which one won?

197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ  ==>  18UGZENCDBHF8ciPUuHFDMDNy1vm8aUmYt  

someone use high Fee to replace orig Txid and got 0.00467224  BTC   ( bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 )

https://mempool.space/tx/354dbcb6fd3532a051e1e363c9122d862949c3d075280d4144f719d6ba99e14a

puzzle 66 is unsafe  

[wilspen]

Can anyone give a rundown on what happened?

Like the original broadcasted transaction, the competing transactions, and which one won?

Take a look at the previous posts and you will understand the context.

Yeah, Bud, I know the concept of this whole test. I wanted to know if anyone took snapshots or notes, of how many different people / competing transactions were happening, before whichever one, finally got through. The play by play, wilspen.

Take a look at the live stream, there you can see the addresses that did RBF and were then overlapped, it happened about 3-4 times.

Maybe your address was there, just look at the time when the mempool website was open and the addresses changed