@@ -30,11 +30,13 @@ infrastructure projects.
30
30
Lightning-Dev mailing list, Richard Myers [ posted] [ eltoo sample ] a link
31
31
to a sample implementation of an eltoo payment flow between nodes on a
32
32
custom [ signet] [ ] . [ Eltoo] [ ] is a proposal to replace LN's current
33
- enforcement layer, which depends on the threat of a penalty for any
34
- party that attempts to use an old channel state, with an enforcement
35
- mechanism that gives the latest state the ability to spend funds from
36
- any earlier state within a certain period. With eltoo, there's no
37
- penalty required, simplifying many aspects of the protocol and reducing
33
+ LN-penalty enforcement layer with a new layer named LN-eltoo.
34
+ LN-penalty prevents counterparty theft by giving nodes the ability to
35
+ financially penalize a counterparty that attempts to publish an old
36
+ channel state onchain. LN-eltoo accomplish the same goal by giving the
37
+ later states the ability to spend funds from earlier states within a
38
+ certain period of time---eliminating the need for a penalty, simplifying
39
+ many aspects of the protocol, and reducing
38
40
the complexity of many proposed protocol enhancements. Myers's sample
39
41
implementation works by using the Bitcoin Core functional test
40
42
framework to simulate payments in an eltoo payment channel.
@@ -78,17 +80,13 @@ infrastructure projects.
78
80
- [ Bitcoin Core #15759 ] [ ] increases the number of outbound connections
79
81
the node will make from 8 to 10. The two new connections will only be
80
82
used to announce and relay new blocks; they won't announce or relay
81
- unconfirmed transactions. Only announcing blocks minimizes the
82
- bandwidth overhead of the new connections and doesn't give spy nodes
83
- information about what node first announced a transaction (i.e. which
84
- node may have created it). These extra two connections increases the
85
- density of connections between network nodes, making it more difficult
86
- to partition the network and execute various attacks possible against
87
- isolated nodes. If no problems are found with this change and the
88
- bandwidth overhead remains small, it's possible the number of
89
- blocks-only peers may be increased in later versions, either as its
90
- own change or in conjunction with other ongoing development such as
91
- [ Erlay] [ ] .
83
+ unconfirmed transactions or ` addr ` peer-discovery messages. Only
84
+ announcing blocks minimizes the bandwidth and memory overhead of the
85
+ new connections and makes it much more difficult for spy nodes to map
86
+ the connections between nodes---a map that can be used by a malicious
87
+ party to attack a node's peers and potentially isolate that node from
88
+ all honest connections, making theft possible (for details, see the
89
+ [ TxProbe paper] [ ] ).
92
90
93
91
- [ Bitcoin Core #15450 ] [ ] allows users to create new wallets for
94
92
multiwallet mode from the GUI, completing a set of GUI actions that
@@ -178,3 +176,4 @@ infrastructure projects.
178
176
[ eltoo summary ] : https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-September/002136.html
179
177
[ signet ] : https://en.bitcoin.it/wiki/Signet
180
178
[ less gossip ] : https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-September/002134.html
179
+ [ txprobe paper ] : https://arxiv.org/pdf/1812.00942.pdf
0 commit comments