--snip--
I could ask for that, so this means they would need to spend the output from the unconfirmed transaction with a higher fee and send it to one of their addresses, right?
yes.
I actually wrote a tutorial a while back on how to execute an cpfp as a sender using electrum. For a receiver, it's actually more or less the same... If you point them towards this thread:
https://bitcointalk.org/index.php?topic=5285192 they can ask for help in case they don't succeed (depends on which wallet they're using tough... It might require them to export private key(s) from their current wallet and import them into electrum if they want to follow the walktrough... In which case they need to be extra carefull not to compromise their keys)
Yes I've seen some of those but they charge way too much. Do you have some that you could recommend?
I've seen good things from viabtc... They have a free and a payed accelerator service, and they're legit... They own a pretty big pool, so they're able to deliver what they promise
It was lower than that. At some point I hoped for it to get purged but it didn't, so it's not low enough for it to get purged but not high enough to get confirmed...
Pruning happens if the limit of the mempool is over the limit set by the node operator OR if the unconfirmed transaction is older than x hours (default 2 weeks). So it should be pruned from most mempools in 2 weeks no matter what the feerate was
I'm not intentionally rebroadcasting but it seems to be happening,
https://live.blockcypher.com displays a received field for transactions and for my transaction it's regularly updated. Do you know how I can know the whereabouts of the rebroadcasts, what triggers them and how many times and when my transaction was rebroadcasted?
To be honest, i have no idear if wasabi automatically rebroadcasts transactions... Maybe you can restore your wasabi wallet from seed by creating a new wallet but re-using the same seed... Not reopening the original wallet untill the transaction has been dropped.
It's also possible you keep rebroadcasting the transaction by your efforts to fix the issue tough... For example: sometimes people start using those "free" rebroadcasting websites because they think it'll fix their problem, but all those sites do is fetch the raw transaction and rebroadcast it, making it harder to double spend or to require more time to wait untill the transaction dissapears from most mempools.
