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/197kFKvMHoRJPXktc8xJwMjeTuE9xijBQAfter this experiment, I realized that the wallet software "Electrum" cannot grab the BTC of #66
we must create own RawTX (raw_hex)
use API broadcasts to blockchain
response = requests.post(
'
https://blockchain.info/pushtx',
data={'tx': raw_tx}
)
print(response.text)
They've made opt-in Replace-By-Fee (RBF) the default in Electrum version 4.4.0. If you want to use the old version without this feature by default, you can install version 4.3.0 using the following steps:
git clone
https://github.com/spesmilo/electrum.gitcd electrum/
git checkout 4.3.0
pip3 install -r contrib/deterministic-build/requirements.txt
pip3 install .
You can use old version of Electrum but every transaction will automatically have RBF enabled on the node.
Only option is to change node in Electrum to your own full-RBF-disabled node.
And
mine in secret this transaction.
However, once the transaction is broadcasted using any (API) method, it is at risk of being replaced.
Even if you share it privately with a third-party miner, that miner could still replace it..
I reached out to major mining pools, and they told me they can't confirm a transaction without it going through the mempool! The pool operators will take the entire reward for themselves, they’ve known about this for a while and are just waiting for it! I don’t even know what to do in this situation... It's frustrating.