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

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

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

Here’s how you can do it in Python:


one-line command in Python

1DWQHdi1mh27vcUyrN5NYB1kWrs3BBKUXA :

197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ :

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

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

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

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

I will join and create my transaction with 6.6 BTC fees 

I also tested mine, and it works. The problem will be when 2, 3, or 50 bots attack the same wallet simultaneously. I have no idea what will happen. This is like roulette; someone will leave the casino with a bag, and some won't. Or will everyone be left empty-handed and the casino (miners) takes everything?


I think it's a bad idea for all of us to have the same cloned bot with the same or similar parameters.

So did this bot work?
Did your bot steal bitcoins the moment you sent the transaction to the network?


We are waiting for you to participate in the trial of Puzzle 66 in the evening.

This is not a public pool, everyone invests their time and knowledge. In this thread and in development, the guys are laying out excellent tools, without which we would not have been able to get to 66 and 130. This is your piece of the pie, but it’s up to you to decide how to use it.

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

Probably when 66, 67, 68, 69 are over 

read again my statement, who's theorizing aimlessly, i just explain it, i'm sick for ppl saying this puzzle has pattern, read again bruh, womp womp.

How can I have this bot of yours, will it be available on github?

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!

Whether this transaction gets replace or not is not going to prove definitively that puzzle 66 will or will not be hijacked when the solver tries to withdraw it (with a public transaction). There are miners that observe the RBF rule and miners that observe the Full RBF rule. So the miner actually produces the block will determine if it is going to get replaced or not.

Finding out how fast the BSGS server is.. And after that it became clear to me what this sentence means.

That is why you need to avoid to those wallets for this purpose, you need to automate the TX somehow without any wallet software.


What part is ridiculous  ?

2 minutes is is too much

#time python3 toddlers_bot.py
INFO:root:Running rsz_rdiff_scan.py...
INFO:root:2024-07-20 00:28:33 - Public Key: 025b2fb64f70afceded779f874ce13407698e406037e0bcd406c1ecec9d1d92880
INFO:root:Extracted Public Key: 025b2fb64f70afceded779f874ce13407698e406037e0bcd406c1ecec9d1d92880
INFO:root:Running command: echo '025b2fb64f70afceded779f874ce13407698e406037e0bcd406c1ecec9d1d92880 2000000000000000:3fffffffffffffff' | nc -v localhost 8080
INFO:root:Keyhunt stdout: 3895508353aa46e8
INFO:root:Keyhunt stdout: Connection to localhost (127.0.0.1) 8080 port [tcp/http-alt] succeeded!

INFO:root:Private Key: 3895508353aa46e8
INFO:root:WIF Key: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYpPyTxb6TR2EXMEW1LL
Daemon stopped
starting daemon (PID 990)
INFO:root:restore_wallet output: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYpPyTxb6TR2EXMEW1LL
INFO:root:load_wallet output:  1DWQHdi1mh27vcUyrN5NYB1kWrs3BBKUXA
INFO:root:history output: {
    "summary": {
        "begin": {
            "BTC_balance": "0.",
            "block_height": 852775,
            "date": "2024-07-18 20:29"
        },
        "end": {
            "BTC_balance": "0.",
            "block_height": 852837,
            "date": "2024-07-19 06:15"
        },
        "flow": {
            "BTC_incoming": "0.00495561",
            "BTC_outgoing": "0.00495561"
        }
    },
    "transactions": [
        {
            "bc_balance": "0.00495561",
            "bc_value": "0.00495561",
            "confirmations": 169,
            "date": "2024-07-18 20:29",
            "fee": null,
            "fee_sat": null,
            "height": 852776,
            "incoming": true,
            "label": "",
            "monotonic_timestamp": 1721327365,
            "timestamp": 1721327365,
            "txid": "098fec25954faad5571bb81234658228c888cd428a2531538ed1d40e278af9e3",
            "txpos_in_block": 337
        },
        {
            "bc_balance": "0.",
            "bc_value": "-0.00495561",
            "confirmations": 108,
            "date": "2024-07-19 06:15",
            "fee": "0.00001152",
            "fee_sat": 1152,
            "height": 852837,
            "incoming": false,
            "label": "",
            "monotonic_timestamp": 1721362520,
            "timestamp": 1721362520,
            "txid": "95e892276c80e888087e14c94d221d8afa49f511087b02639eaa99b6b36d5bc6",
            "txpos_in_block": 336
        }
    ]
}
 
INFO:root:bumpfee output: No Transactions to bumpfee
Daemon stopped

real   0m13.485s
user   0m5.462s
sys   0m0.248s

This is ridiculous

yesterday , I am online and use Kangaroo.exe crack private key about 2 minutes
then I import private key to Electrum  ( Win10 )
I got 2 transaction notifications immediately, one was +0.00495561  BTC , the other was -0.00495561 BTC , while the balance was 0 BTC
At the time , Transaction is  0  confirmations  , but I can't do anything ....
Electrum show the balance 0 BTC