I use a dapp that control the btc wallet, so all txs were handle by that dapp.
It's inscribe.app, basically they connect to evm wallet and generate a btc wallet and assign that wallet to my evm. i made a withdraw from that wallet and this happen to me.
This escalated from an easy RBF procedure into a very complicated private key export, encode to WIF prvKey, import to other wallet to make the replacement transaction.
That's basically what you need to do
only if it's possible to export the correct private key that can derive the correct address.
But upon testing "
inscribe.app", I've failed to reproduce the TapRoot address from the private key indicated in the (
hidden) "
EVM Private Key" or from the prvKey of the connected wallet.
There must be something else at play there that may require some technical documentations or a quick look at their source code (
if open-source),
But unfortunately, neither of those are available.
I'm afraid that your second best option is to utilize CPFP to the change of the child txn or bump that child txn to further increase the overall transaction fee.
And do not base the "
overall fee rate" from the child transaction's fee rate since its size is a lot smaller than the parent.
For example, the child would need an additional 56,300 satoshi "
absolute fee" on top of its own fee to bump the parent to 10sat/vB.
That also relies on the node where you'll broadcast it since it's now dropped from some nodes' mempools.
I mean, a huge amount of very small inputs (if it would not be SegWit it would be considered dust!) with an tx fee so low I didn't see that for months.
Why would a business send your money in "something smaller and heavier than pennies" and make you pay for the "lorry" to transport them?!
Ordinals NFT.