~snip
I've been away for days, not with my laptop to check the settings, will do so when i get home tomorrow.
The major feature I'm still anticipating on Electrum mobile is bulk transactions like sending to multiple addresses at a time because it actually saves fees.
The way Electrum does it is to have desktop more advanced and flexible than mobile, it might come soon in mobile but anyone running several bulky transactions is better off using desktop than mobile, desktop is further customizable, to me safer than using mobile.
Thanks Obim34 for this good post which will help a lot of our LB users in what they do regularly. However, and for the purpose of discussion, I want you to make some clarification so that we are all on the same page. When you say "CPFP helps pushes stuck transactions by creating a new transaction", are you saying that the new transaction to the same receiving address will not lead to the sender paying more than he was supposed to pay? In other words, when you send the second transaction with a higher fee, what will be the value of the transaction? Won't the transaction make the sender to pay more than he was supposed to pay? In terms of numerical values, assuming I want to send 0.5mBTC to someone but the transaction refuses to go thereby necessitating the need to use CPFP, won't I be sending more than 0.5mBTC aside the fee? Please clarify so that everyone will understand.
When we say a transaction is stuck, it means it hasn't gotten any confirmation, having confirmed 1 Block through confirmation it is no longer available that means miners has already accepted the transaction, neither RBF or CPFP will work. Confirmation should be 0 Block for a long time.
The receiver is basically the one doing CPFP, lets say mister A sent me 10$ bitcoin and me the receiver mister B wants to spend that same amount of $10 bitcoin to mister C (but the transaction is stucked), i then create a child transaction sending the exact amount including mister A output inside my new transaction with enough fee to cover for both, miners now sees my new transaction and accepts both because my new transaction is depending on what Mister A is sending to me (can't move that exact amount when it hasn't been confirmed in my wallet first, that means miner validates Mister A sending to me before validating my own new transaction to Mister C )CPFP happens with bigger fees than RBF.
RBF (Sender adjusts) CPFP (Receiver Adjusts)