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

[bug]: Don't allow unconfirmed Inputs for Channel Openings which are used/labeled by the sweeper subsytem. #8543

Closed
ziggie1984 opened this issue Mar 12, 2024 · 1 comment · Fixed by #8545
Assignees
Labels
bug Unintended code behaviour funding Related to the opening of new channels with funding transactions on the blockchain

Comments

@ziggie1984
Copy link
Collaborator

Make sure we don't use sweeper related unconfirmed outputs for channel openings. Because those Inputs are actively rebroadcasted leading to RBF situations. This is especially critical for zeroconf channels which could potentially RBFed without the operator of the Channel noticing leading to fractional reserve problems where the node operator allocates more funds into channels than he actually has.

@ziggie1984 ziggie1984 added bug Unintended code behaviour needs triage labels Mar 12, 2024
@ziggie1984 ziggie1984 self-assigned this Mar 12, 2024
@ziggie1984 ziggie1984 added funding Related to the opening of new channels with funding transactions on the blockchain and removed needs triage labels Mar 12, 2024
@ziggie1984
Copy link
Collaborator Author

relates to #8540.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended code behaviour funding Related to the opening of new channels with funding transactions on the blockchain
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant