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

[RFC/WIP] Core: make sure RBF is enabled #135

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

knocte
Copy link
Collaborator

@knocte knocte commented Oct 21, 2020

Lightning transactions should always be RBF enabled, because the
miner fee rates can vary wildly since the moment they are signed
until the moment they are broadcasted.

Lightning transactions should always be RBF enabled, because the
miner fee rates can vary wildly since the moment they are signed
until the moment they are broadcasted.
@joemphilips
Copy link
Owner

All LN involved TX specifies sequence value explicitly in BOLT03, so we don't need this. In fact in the case of TX which requires two signatures, we only exchange the signature and not TX itself so the shape of the TX must be precisely defined.

@joemphilips
Copy link
Owner

Miner fee problem is addressed recently by option_anchor_output feature, which is not reflected in this library yet :(

@joemphilips
Copy link
Owner

See bitcoin-optech newsletter for option_anchor_outputs

@knocte
Copy link
Collaborator Author

knocte commented Oct 28, 2020

Miner fee problem is addressed recently by option_anchor_output feature

Anchor outputs currrently has a limitation/bug: https://lists.linuxfoundation.org/pipermail/lightning-dev/2020-September/002796.html TL/DR: watchtowers are ineffective.

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

Successfully merging this pull request may close these issues.

2 participants