Quote from: Cricktor on Today at 01:21:01 AM

Quote from: invisibleecho on Today at 01:10:20 AM

As soon as there is a confirmation on the blockchain, the corresponding public key of said wallet is exposed to the public and it's not really hard to write a bot which checks the latest transaction history from any wallet.

No, this is wrong, you don't need to wait for a confirmation. As soon as a low entropy puzzle withdrawal transaction is in public mempool, still unconfirmed, the public key is revealed and bots can make advantage of that.

Ah right my bad, you're 100% correct. As soon as the transaction is broadcasted to the network it becomes publicly visible.

Quote from: Cricktor on Today at 01:21:01 AM

Quote from: invisibleecho on Today at 01:10:20 AM

Apart from that, I would likely try to get my timing right and combine it with Mara's slipstream, which I personally have never used, but will when I manage to find some private keys.

How does "timing" help you when you don't know when Mara pool will find a valid block? And block intervalls are only statistically average every about 10min with an observance window of 2016 blocks. You can be unlucky, like the intervall between blocks 878012 and 878013 or blocks 877956 and 877957 or ...

The closer your transaction is to being mined (i.e., the shorter the remaining time in the current block cycle), the less time the attacker has to act.
My idea was to reduce the time any potential attacker has. Maybe I'm wrong though, still learning about blockchain

In the end, it doesn't really matter until anyone finds a low entropy private key.