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

Non-zero-fee anchors support was removed #1822

Closed
devrandom opened this issue Nov 2, 2022 · 4 comments · Fixed by #1828
Closed

Non-zero-fee anchors support was removed #1822

devrandom opened this issue Nov 2, 2022 · 4 comments · Fixed by #1828

Comments

@devrandom
Copy link
Member

#1685 effectively removed support for non-zero-fee anchors. However, VLS still needs to support these for now, and we are using LDK utilities for transaction building.

Cc @wpaulino

@TheBlueMatt
Copy link
Collaborator

Hmm, we asked before we landed this and CLN folks (actually responded after #1685 (comment)) indicating it was okay to go ahead and CLN would be moving to 0-fee-htlc anchors ASAP so there's little reason to support this anymore.

I'm not super excited about adding parallel util methods to construct non-0-fee HTLC anchor txn just for something that won't go into prod.

CC @cdecker can we get some clarity on where y'all are with this?

@ariard
Copy link

ariard commented Nov 3, 2022

From my memory, the non-0-fee HTLC anchor txn was ever only deployed by LND. option_anchors_zero_fee_htlc_tx was in nurturing before any other impl worked seriously on anchor support.

@devrandom
Copy link
Member Author

From what I understand, CLN has only non-0-fee anchors right now.

@TheBlueMatt
Copy link
Collaborator

IIUC, when CLN implemented anchors they didn't actually (initially) implement spending anchors, just building the tx format but continuing to operate "as normal". This would mean that 0-fee HTLC txn wouldnt work, so they didn't go that way with their very first implementation.

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 a pull request may close this issue.

3 participants