Quote from: benjaniah on July 29, 2024, 05:36:35 AM

Quote from: sdhgfdsjfgsiujdgf on July 18, 2024, 03:36:14 AM

Quote from: nomachine on July 15, 2024, 03:41:23 PM

Quote from: sdhgfdsjfgsiujdgf on July 14, 2024, 09:32:46 PM

Quote from: benjaniah on July 14, 2024, 02:55:16 AM

So, has anyone figured out a bulletproof way to spend puzzle 66's inputs, once the key is found, without the internet-of-bots stealing the prize? Other than trying to find a big enough mining pool that will mine your transaction into a block and not expose the transaction to the mempool? Could any mining pool even be trusted to that extent?

I cant belive that I read this BS again on this forum. Are you out of your mind? Why the hell do you need a mining pool? Huh

I have read a similar BS from another user in another topic, that is talking about miners.

You dont need any miners to get the money, when you got the privatekey, you can immediately take control of the bitcoins. Do you really dont know how?

It's a blast to solve Puzzle 65, 66, 67, 68. It takes about 60 seconds once we identify the public key from the blockchain.

Here i tested my toddler bot script on Puzzle 65 = address -> 18ZMbwUFLMHoZBbfpCjUJQTCMCbktshgpe

root@puzzle ~/Test # time python3 toddler_puzzle_bot.py
Version 0.2.230519 Satoshi Quest, developed by AlbertoBSD
Endomorphism enabled
Threads : 12
Search compress only
Quiet thread output
K factor 4096
Mode BSGS sequential
Opening file 65.txt
Added 1 points from file
Bit Range 65
-- from : 0x10000000000000000
-- to : 0x20000000000000000
N = 0x100000000000
Bloom filter for 17179869184 elements : 58890.60 MB
Bloom filter for 536870912 elements : 1840.33 MB
Bloom filter for 16777216 elements : 57.51 MB
Allocating 256.00 MB for 16777216 bP Points
Reading bloom filter from file keyhunt_bsgs_4_17179869184.blm .... Done!
Reading bloom filter from file keyhunt_bsgs_6_536870912.blm .... Done!
Reading bP Table from file keyhunt_bsgs_2_16777216.tbl .... Done!
Reading bloom filter from file keyhunt_bsgs_7_16777216.blm .... Done!
Thread Key found privkey 1a838b13505b26867
Publickey 0230210c23b1a047bc9bdbb13448e67deddc108946de6de639bcc75d47c0216b1b
All points were found
Private Key: 1a838b13505b26867
WIF Key: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZM21gaY8WN2CdwnTG57
Starting Electrum ....
starting daemon (PID 41802)
true
Keypair imported: 18ZMbwUFLMHoZBbfpCjUJQTCMCbktshgpe
Transaction IDs: []
Daemon stopped
Electrum daemon stopped successfully.

real 2m46.311s
user 1m55.133s
sys 0m59.598s

and the time required to import the key into Electrum and start the redirection of transactions (if they exist ).

The 10 minutes is the average time and this is a pretty stupid circumstance. At this stage, the transaction has
entered the mempool and remains 'Pending,' waiting for confirmation.

It only takes a matter of seconds (for such a small range) to obtain the private key from public key, after which
you (or a thousand of them) can replace the still-unconfirmed transaction in the mempool.

In other words, you need a very strong miner to speed up (prioritize) the transaction to go through the mempool in
one (or less than) minute for puzzle 66, 67, 68, 69.

Are you replying to me, or just randomly hallucinating? What is the purpose of your writing?

If (hypothetically) you found the private key for puzzle 66, and simply tried to spend puzzle 66's BTC balance to another wallet that you control, you better hope that that transaction gets mined into the next block
within a few seconds, or it will be stolen with 100% certainty. This is also the case for the next few puzzles, 67,68,69...

The only way to do that is to use the MARA Pool Slipstream. The transaction was mined before the public key entered the mempool.