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

BOLT 5 : data_loss let you salvage received HTLC on remote commitment #639



None yet
2 participants
Copy link

commented Jul 11, 2019

Thanks to data_loss_protect, your remote peer is going to give you his current per_commitment_point if channel_reestablish are exchanged. If he owns a fully-signed commitment_transaction and broadcast it, using your basepoints you should be able to derive keys even for remote_htlcpubkey and get back, non only your to_remote output, but also HTLC outputs.


This comment has been minimized.

Copy link

commented Jul 11, 2019

The assumption here is that if you're behind in commitment state, then you likely don't also have the required information to reconstruct the HTLC script itself.


This comment has been minimized.

Copy link
Contributor Author

commented Jul 12, 2019

Oh right, was thinking only in a key derivation side, agree it's highly likely you won't have preimage/timelock to rebuild scripts

@ariard ariard closed this Jul 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.