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

Update commitment transaction design to support blinded outsourcing #59

Closed
Roasbeef opened this issue Oct 21, 2016 · 1 comment
Closed
Labels
advanced Issues suitable for very experienced developers commitments Commitment transactions containing the state of the channel p2p Code related to the peer-to-peer behaviour
Milestone

Comments

@Roasbeef
Copy link
Member

At the Lightning Summit, we decided to switch the design of the commitment transaction's to support the proposed blinded channel outsourcing scheme. The commitment transaction itself, the secrets generated as part of a new channel, the funding workflow messages, and the channel state-machine itself need to be updated as a result.

@Roasbeef Roasbeef added advanced Issues suitable for very experienced developers commitments Commitment transactions containing the state of the channel p2p Code related to the peer-to-peer behaviour labels Oct 21, 2016
@Roasbeef Roasbeef added this to the Lightning V1 Specification milestone Oct 21, 2016
@Roasbeef Roasbeef modified the milestones: v0.3-alpha, v0.2-alpha Mar 29, 2017
@Roasbeef
Copy link
Member Author

Fixed.

mrfelton pushed a commit to LN-Zap/lnd that referenced this issue May 10, 2024
…ate-dependency

build: workflow allows to use private `btcwallet-strike` dependency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced Issues suitable for very experienced developers commitments Commitment transactions containing the state of the channel p2p Code related to the peer-to-peer behaviour
Projects
None yet
Development

No branches or pull requests

1 participant