summaryrefslogtreecommitdiff
path: root/4d/03e04bedcf09d71fcc072c33d2f5c989774e93
blob: 6a302232015de5d55fa19f22f3f45a3cc15fb5e0 (plain)
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
Return-Path: <kanzure@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id DF940409
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 11 Aug 2015 18:51:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com
	[209.85.213.171])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 25EF01CB
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 11 Aug 2015 18:51:01 +0000 (UTC)
Received: by igfj19 with SMTP id j19so78647460igf.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 11 Aug 2015 11:51:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=aZbqrXhnbURDNz6C4QdQX480PV/OWIacsn5FK0L3kKw=;
	b=uJEW3C/arRkC98V0sqVK+S1SLV7dpcOJhx5O1VqbQqDETXs9EY8A3CAJ2fS/jHFyEf
	AnTZ+YWZ/f8Y2+M3TyI1IrAlHwqv7zo70qYqegyWWvYCLtnKD10Wdqr4oFVmG+7PnmaJ
	AaTVVIDOEnUqLdJYJv6MGisKrC2rcFXtHtJVdX9x46GZGinAeTQDQDNARiX8uvrlRLLg
	VVCTt8ZHgWSlaLiWcFCHhHeE/yMx31E0Y56j7PWHbCAnjMqmZzn925IdNhhLfZtXP2DY
	MuaBFNE6jwKNTxH/FJzcSAEbla2vtdTphtjMHe8NBy6PAHqIuAWeVOE/Vy4NKMOs6wTq
	QBaQ==
MIME-Version: 1.0
X-Received: by 10.50.79.196 with SMTP id l4mr18536665igx.48.1439319060605;
	Tue, 11 Aug 2015 11:51:00 -0700 (PDT)
Received: by 10.36.91.135 with HTTP; Tue, 11 Aug 2015 11:51:00 -0700 (PDT)
In-Reply-To: <CALgxB7sQM5ObxyxDiN_BOyJrgsgfQ6PAtJi52dJENfWCRKywWg@mail.gmail.com>
References: <CABsx9T16fH+56isq95m4+QWsKwP==tf75ep8ghnEcBoV4OtZJA@mail.gmail.com>
	<CABm2gDpwMQzju+Gsoe3qMi60MPr7OAiSuigy3RdA1xh-SwFzbw@mail.gmail.com>
	<CABm2gDoz4NMEQuQj6UHCYYCwihZrEC4Az8xDvTBwiZDf9eQ7-w@mail.gmail.com>
	<8181630.GdAj0CPZYc@coldstorage>
	<CABm2gDp2svO2G5bHs5AcjjN8dmP6P5nv0xriWez-pvzs2oBL5w@mail.gmail.com>
	<CALgxB7sQM5ObxyxDiN_BOyJrgsgfQ6PAtJi52dJENfWCRKywWg@mail.gmail.com>
Date: Tue, 11 Aug 2015 13:51:00 -0500
Message-ID: <CABaSBawGLwbQroJgohYW-FcO7zeGJk7awh+UnLwoZOoaQKaKyA@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
To: Michael Naber <mickeybob@gmail.com>, Bryan Bishop <kanzure@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fees and the block-finding process
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 11 Aug 2015 18:51:02 -0000

On Tue, Aug 11, 2015 at 1:46 PM, Michael Naber via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Note that lightning / hub and spoke do not meet requirements for users
> wishing to participate in global consensus, because they are not global
> consensus networks, since all participating nodes are not aware of all
> transactions.

You don't need consensus on the lightning network because you are
using bitcoin consensus anyway. Commitment transactions are deep
enough in the blockchain history that removing that transaction from
the history is impractical. The remaining guarantees are ensured by
the properties of the scripts in the transaction. You don't need to
see all the transactions, but you do need to look at the transactions
you are given and draw conclusions based on the details to see whether
their commitments are valid or the setup wasn't broken.

- Bryan
http://heybryan.org/
1 512 203 0507