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

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

perfect, since you are the guy, tomorrow at 15:30 (UTC -3. Brasilia Time), the creator will do the transaction and expose the public key, put your knowledge into practice and prove what you are saying, otherwise , and if it is not hacked, it can be said that we still have hope.

puzzle 63 in ~8 Seconds


Thanks for this info. This is genius for a bot.

Well is interesting know what you are doing, maybe i test it in the future.

To "preload" the files in memory I actually use the BSGSD  (bsgs daemon)


https://github.com/albertobsd/keyhunt/blob/main/BSGSD.md

It is a keyhunt server that only run BSGS for some small ranges like 66 bits it listen in a TCP socket on some PORT for incoming jobs, this is a public key and range to scan it only returns the private key if that was found or "404 NOT FOUND", check the link above for more information.

his audience is on YouTube, a channel for Brazilians who speak Portuguese, I brought it here to show you since we are testing technology, the more people the better, that's why he has an appointment with his audience in Brazil, which is the time he can do the live.

I'm more interested in the techniques you use to preload files like:

keyhunt_bsgs_4_4294967296.blm

Mine range from 14 to 32 gigabytes. 😄

I’ve tried several techniques:

/etc/udev/rules.d/99-nvme-readahead.rules


Some of these methods can speed up loading by up to 10 seconds.

I think that is the hour he can sit down and do his streaming


Well first there is not such thing as "Cancel Transaction" even if the wallet call it as is. In reality it is just a Full RBF tx to a new wallet still owned by you.

And that is just a software feature of some wallets, if I do that with a script it don't care about the Virtual "Zero Balance" it only does a new TX with the available utxos for that address regarless if they are waiting confirmation in mempool, that is actually the whole point of Full RBF

It is not the same to send 6.6 BTC and 0.0045 BTC. We need a list of transactions that recently sent 6 BTC to see how long it takes so that we can draw a conclusion. If sending 6 BTC takes 30 seconds, I will give up using the bot.

Your testing would have been successfully completed yesterday if you had kept the private key in the correct range. No worries, just be mindful of it this time. If the funds you sent go to this address (1ND6VxAAdamzix1ZffoZww78YcMZQAWDEa), understand that I have won this Bot race. I invite all bots to participate in this race. Let's see something new tomorrow ... after a long time.

Edit:
Wait a moment. Why are you giving us a specific time? There is no fixed time for the transaction of puzzle 66. Just complete this task at any time tomorrow and let all the bots do their work.

I will show you part of my latest script. It uses Iceland's rsz_rdiff_scan.py to obtain the public key....

---snip---

faith belongs in the church. Even if you don't like to hear it, it doesn't matter what you or I think, feel, hope or believe. What counts are the facts, and these are implemented in the Bitcoin protocol, can be read and reproduced. It's a program, it has a way of working and it will stick to it

This topic has already been dealt with many times on previous pages, including links to the technical explanations. It is completely irrelevant which software you use, whether you activate RBF or not. I would highly recommend that you read and study the technical documentation on this topic.