pull down to refresh

I send a txn from joinmarket (JAM) and RBF was not available, my transaction is stuck in the mempool for days now, and it does not look like it is going to go thru.
what are my options?
If you see the transaction in your "destination" wallet, use Sparrow or Electrum and click on the tx and select CPFP (Child pay for parent). Then you have the option to pay a fee higher for that tx. Or even in Bitcoin core you can do that but on command line.
Or wait.
reply
This worked for me, thanks much
reply
Child Pays For Parent (CPFP) from the wallet you sent it to
reply
I had the same problem this past month. It took 20-ish days for it to drop out so I could retry with a higher fee.
So, don't worry. Just give it time.
reply
𝐇𝗼𝐰𝐝𝐲 𝐝𝗼 ? 🀠 πŸ‘‹
reply
If you own the wallet receiving the transaction, you can create a new transaction with a higher fee to send the pending UTXO to yourself.
Or, grab a cup of coffee and wait it out.
reply
That would be a tourist attraction sized cup of coffee sometimes. There must be loads of stuck transactions lately though. Mempool has almost not ever been back under 300mb since the udinals plague started.
Unfortunately a lot of wallets refuse to let you spend pending payments at all. Which ones that you krow of do this? I think Core can do it, there might be others.
I had a stuck transaction recently too, in the early days of the ordinal spamfest. both sides of the transaction were custodial and neither side cared to fix the problem. Took 5 days to finally clear.
Definitely an argument against custodial wallets in the circumstances, I think you can say.
reply
Electrum and Sparrow both let you do this. IMO any wallet that doesn't let you do the following is a no-go for me:
  • CPFP/RBF
  • Send to many (saves a lot in fees, I pay for some bills in BTC and with this I can pay them all in one transaction)
reply
Why do we use the blockchain at all, then?
If all transactions that are stuck in the mempool right now can be spent, then basically, we can use the entire mempool as one big ass shared Lightning channel.
Added benefits:
  1. we don't need to open and close channels.
  2. channel balancing isn't needed, or even possible.
πŸ₯³
reply
Because without Proof of Work it's not possible to get every node to agree on the state of the system.
Google the Byzantine General's problem to learn more
reply
Proof of work is a distributed random selection algorithm, or, as I often say, a lottery. But what makes it so there can be total agreement is the magic spice that Satoshi brought, the notion of hash weight as a discriminator for concurrent solutions.
Nodes keep the abortive offshoots that fork here and there as the inevitable sub-12 second concurrent solution discovery always makes the odd side branch.
Yes, indeed, you could say that nakamoto consensus is not a blockchain but more like a vine, with a central leader and small and short branches like the spiral grabbers on grapes or passionfruit. A block-vine. I don't think it will stick, but blocktree sorta sounds cool and it's almost valid, if you can call it a tree when it cannot grow laterally.
reply
LN cannot work without onchain and onchain cannot scale without LN. Each LN payment is actually an onchain atomic tx that is not YET broadcast.
Please start reading and learning before saying such stupid things. https://bitcoin.page https://lightning.how
reply
Full RBF/Out of band payments lmao
reply
This happened to me a few times, when things got busy and my usually ok low fee didn't get any attention. After a while it gets dropped and your transaction is effectively cancelled. There's nowhere else it can go.
reply