Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add fee bumping functionality #1261

Open
hsjoberg opened this issue Jul 4, 2023 · 2 comments
Open

Add fee bumping functionality #1261

hsjoberg opened this issue Jul 4, 2023 · 2 comments
Assignees
Milestone

Comments

@hsjoberg
Copy link
Owner

hsjoberg commented Jul 4, 2023

No description provided.

@hsjoberg hsjoberg added this to the 0.7.0 milestone Jul 4, 2023
@hsjoberg
Copy link
Owner Author

Related PR #1319

@Darth-Coin
Copy link
Contributor

Please add a functionality to bump the fee for force closed channels.
I have a FC for 2 months pending and can't do anything.

I had a channel with Coingate, working just fine.
Then I sent few sats to a zeuspay LN address (hold invoice).
In my Blixt appeared as "open".
The receiver confirmed that was received in his Zeus node.
I even kept my Blixt in persistent mode for many hours.
After 5 days, I reopen my Blixt and the channel with Coingate, through which that hold invoice was paid, got force closed. And seems to be triggered from my side, not from Coingate side.
The FC was sent with a 10sat/vB and got stuck in mempool without any option to bump the fee.

For weeks I just re-broadcast the tx using mempool and https://bitaccelerate.com, just to keep it "alive" in the mempool and not be kicked out.

Then I deposited 100k sats to Blixt onchain, hoping that will be re-broadcast with a higher fee from that new UTXO.
It doesn't. Seems that force close channels cannot be bumped with a higher fee automatically.

Please add a functionality like Zeus have, to bump the fee manually for a pending tx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants