Quote from: kTimesG on Today at 01:32:46 PM

Quote from: Frequence on Today at 01:25:38 PM

Burned that $100 in fees.
Miners: Thank you, bro.

Code:

2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Monitored addr: 1FXsMVXVV52zyLhHzZKg6wGous6KzMW6bM
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] RIPEMD-160: 9f6845cc702a6b162fce0255387c8f7c609d72e6
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Mon UTXO: a39c45e65f35ff4398d98332fa3f4b6aaabe1316391711441b00556803b89f29 {0}
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Mon UTXO: abfbbafd607c51d723b321a632967bb12fb23642a03b52ddc76be6166e9f773b {1}
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] maxOutVal: 98363 estTxSz: 339 useful UTXOs: 2
2025-06-24 13:21:56,174 [INFO ] [p71_3dm] [MP] Found unconfirmed TX
2025-06-24 13:21:56,175 [INFO ] [root] Processing TX ID: bb74f418b8b8ea18bb1c81451d7059a79e36a11289de3a765b9e71cd370fa694
2025-06-24 13:21:56,175 [INFO ] [p71_3dm] [MP] TX fee: 14366 sat; 42 sat/vB
2025-06-24 13:21:56,175 [INFO ] [root] [p71_3dm] Solving pubKey: 0216aebfc21a9b8c831a4dba02bdb08067fcd7b96a6f2f6ce2ed5300993ebc3be1
2025-06-24 13:21:59,384 [INFO ] [p71_3dm] Private key: 0x42341f438010c1b651
2025-06-24 13:21:59,385 [INFO ] [p71_3dm] Full-width private key: 000000000000000000000000000000000000000000000042341f438010c1b651
2025-06-24 13:21:59,386 [INFO ] [root] New key: 463f1adbfeb068e1981302eed3adb9ceb387dda6f90145b4cf92f856447db129
2025-06-24 13:21:59,386 [INFO ] [root] New address: 1Gw9sm693wfvMr11g6M1NuqtEnF8FFniyG
2025-06-24 13:21:59,387 [INFO ] [root] Creating TX with out value 83658

etc... fought to the very end.

Thx for the exercise though.

Quote from: 3dmlib on Today at 01:31:26 PM

Is it possible to limit maximum fee somehow? Any ideas?
Also, where to view all mempool RBF timeline? mempool.space definitely not shows all.

Did you scroll the RBF timeline on mempool.space? It shows the TX has been replaced 51 times.

Two of those were mine. But looking at the timeline, it seems that the owner of the address 158tuQVCj6DTPxBawCFQcpiVVs5qkmieLY was replacing its own TX many times in a row, which is a hint of a bad coded bot.

@kTimesG

Can you please share your bot script? Thanks