Skip to content

Newsletter 66: correct Eclair DLP bullet #231

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 2, 2019
Merged

Newsletter 66: correct Eclair DLP bullet #231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions _posts/en/newsletters/2019-10-02-newsletter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,10 +116,19 @@ projects.
tested by the patch author produced about 38.0 MB in allocations.

- [Eclair #1097][] begins deriving channel keys from the funding pubkey,
preparing Eclair for using the data loss protection scheme described
in [Newsletter #31][dlp footnote]. This only applies to new channels
allowing Eclair to use the Data Loss Protection (DLP) scheme described
in [Newsletter #31][dlp footnote] even if all data has been lost.
This does require the user recall the node they opened their channel
with and find the channel id (which is public information for public
channels).
This only applies to new channels
opened after updating to a version of the software implementing this
change; old channels are unaffected.
change; old channels are unaffected. *(Note: an earlier version of
this bullet mistakenly claimed this merged PR would make it possible
for Eclair to add DLP support. Instead, Eclair already had DLP
support and this PR changed how the channel keys are derived in order
to make that support useful even if all data is lost. Optech thanks
Fabrice Drouin for reporting our error.)*

- [C-Lightning #3057][] makes it possible to use postgres as
C-Lightning's database manager.
Expand Down