1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
Return-Path: <lee.chiffre@secmail.pro>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 73DAFC0733;
Tue, 14 Jul 2020 02:58:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by fraxinus.osuosl.org (Postfix) with ESMTP id 6FB5088D7D;
Tue, 14 Jul 2020 02:58:13 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id G0imNICkhINA; Tue, 14 Jul 2020 02:58:13 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from secmail.pro (secmail.pro [46.226.111.104])
by fraxinus.osuosl.org (Postfix) with ESMTP id CDB8988CC0;
Tue, 14 Jul 2020 02:58:12 +0000 (UTC)
Received: by secmail.pro (Postfix, from userid 33)
id 39AA440EAF; Tue, 14 Jul 2020 04:58:12 +0200 (CEST)
Received: from secmailw453j7piv.onion (localhost [IPv6:::1])
by secmail.pro (Postfix) with ESMTP id 5A0FE2511FF;
Mon, 13 Jul 2020 19:58:10 -0700 (PDT)
Received: from 127.0.0.1
(SquirrelMail authenticated user lee.chiffre@secmail.pro)
by giyzk7o6dcunb2ry.onion with HTTP; Mon, 13 Jul 2020 19:58:10 -0700
Message-ID: <6443d6fb7ba06151b8a4ff4914761471.squirrel@giyzk7o6dcunb2ry.onion>
In-Reply-To: <f0372f8eec5878fd919b654db76aeff7.squirrel@giyzk7o6dcunb2ry.onion>
References: <f0372f8eec5878fd919b654db76aeff7.squirrel@giyzk7o6dcunb2ry.onion>
Date: Mon, 13 Jul 2020 19:58:10 -0700
From: "Mr. Lee Chiffre" <lee.chiffre@secmail.pro>
To: lightning-dev@lists.linuxfoundation.org
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Mailman-Approved-At: Tue, 14 Jul 2020 13:29:35 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Lightning - Is HTLC vulnerable? And mention of
Channel Factories
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2020 02:58:13 -0000
Sorry. Re-sending with correction to CC bitcoin-dev
I am sorry if this was already brought up in previous threads. If I know
lightning network correctly then HTLC is used to enforce settlements on
blockchain if there is a dispute. Could a person lose money if their HTLC
does not get confirmed in the timeframe or if an older HTLC gets
confirmed first? I see different ways this could happen.
One, if the blockchain is very saturated with other transactions. The
reason we need lightning network is why it might have troubles with
settlements? Two, competition from a different conflicting HTLC. A newer
HTLC might not get confirmed before an older HTL. Three, denial of service
the lightning router so they never have a chance to send a settlement
HTLC.
I found out about a recent attack technique that sounds like it might be
similar called "flood and loot".
Is this a concern on lightning network? I humbly say that I do not fully
understand all of lightning network yet. I am working to grasp the idea.
These are questions I look to find answer for. Another question I have. I
did read the paper Scalable Funding of Bitcoin Micropayment Channel
Networks. Would channel factories be better and eliminate my concern?
I am sending this to lightning-dev mailing list. I do not see
lightning-dev emails because google recaptcha blocks me from the
subscribe. Please CC me if you reply so I can read it.
--
lee.chiffre@secmail.pro
PGP 97F0C3AE985A191DA0556BCAA82529E2025BDE35
|
