Quote from: wilspen on Today at 03:33:42 AM

Alberto, there is a tool on the Binance website that allows you to pay a higher fee and have the transaction mined quickly, doing this transaction through Binance runs the risk of losing the BTC too, or it's the same, regardless of the place, it would only be safe directly with a miner?

It is NOT safe, most of those services only works with Transactions already stuck on mempool.

Quote from: k3ntINA on Today at 06:42:49 AM

I don't know, maybe I'm wrong, but what I noticed is that your transaction was not broadcast from the Mempool route. I think you know a way.

The history here has two networks, one is the main one and the other is the main Mempool route, the transaction was not confirmed on the Mempool route, although it was sent earlier, but it was not approved, and maybe the Mempool policy behaved like this. but your transaction did not pass through the Mempol route, am I wrong? ?

https://blockchair.com/bitcoin/address/197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ

Thank you for sharing your research, I think that once the TX Is mined then that page move it from mempool to main, most pages discard all other TX once that the block is mined and those transactions are market as invalid or with conflicts ( because the utxo is already mined )

I already share how to I do it. I don't do anything special or different.

Quote from: jacky19790729 on Today at 09:00:52 AM

use API broadcasts to blockchain

response = requests.post(
'https://blockchain.info/pushtx',
data={'tx': raw_tx}
)
print(response.text)

thank you i didn't know this API i will add to my script as backup method

Quote from: kTimesG on Today at 09:26:31 AM

The question is why didn't the bot work as expected, ideally the experiment should have resulted in all the BTC being burned into the fee (or at least a lot more TX than 3 or 4).

It seems the mempool rejects some TX even if the fee is substantially higher. There's something alberto does not tell us, or he was just very lucky. Or maybe the mempool push TX api was the secret sauce that worked.

Some ideas:
- spam the mempool with multiple TX with different output addresses and fees
- broadcast the TX to multiple destinations

I don't do anything special.

- spam the mempool with multiple TX with different output addresses and fees

each time that the transaction fail I increment the fee by 10% and resend it until it was accepted by the mempool API, then my bot sleep for 30 seconds just to recheck if my previous TX is still the higher transaction fee if no, then it repeat the process again

Quote from: AlanJohnson on Today at 12:38:51 PM

Ok ... So why all the puzzles with lower ranges are still sitting there ? Why nobody can crack puzzle 130 ? If that would be possilble all the puzzles would be empty now and every day we would be hearing about stolen bitcoins after making transactions (and releasing public key).

Beacuase we don't know the public key of those, the public key is only know if the address made a outgoing transaction. Until that those address are “safe”