Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 86. (Read 244737 times)

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.

Can anyone give a rundown on what happened?

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

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

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.

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

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

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

@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?

pip3 install requests

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

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

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

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

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

This is not fair. How can we get a piece of cake?

Yes, I agree with this. I've observed some unusual occurrences because not all miners adhere to the same rules. There have been instances where transactions with lower fees were mined instead of those with higher fees, such as 20 satoshis per virtual byte (sat/vB) being chosen over 200 sat/vB. This happens because not all miners promptly update their block templates when a transaction's fee is increased by a bot. Therefore, even if you offer the highest fee, there's no guarantee you'll win the mining competition.

I just finish my bot, i just did a test in mainnet for address: 1Sk4K8upb9beiKZtxnbN6DYLkHWhhKf5Z

First TX for reveal the Publickey was 1sat/vB 5bc8a39149f4f5a421418d36c173d941053b39ad896aa1d986a0e1e7e2e14471  (This trigger the bot)

TX made fully automated with  8sat/vB is 88e918f1d5a92640036a913d2eae6f6f55619161a8bd4ec6641c3372138f0047
And some oher with 12 and 16 sat/vB
9c27f54778b3642a99baefaad748bb2fa1633209d71a2abb5115377974f1e7a6
9657ead0a66aade90b48d25d43252172e905f232ec081c2cc14a3bbb91dd7f62

All TX were made by the bot full automated

TX where broadcasted using the mempool.space API

https://mempool.space/docs/api/rest#post-transaction

Sometimes i get some weirds errors like:


This is because i was stoping the bot and starting it again, just to try to catch those errors:

Something that helpme to do a lot of test with a single TX was that the previous block was mined half hour before




I am glad that you like it!

This is not fair. How can we get a piece of cake?