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
|
Return-Path: <rusty@ozlabs.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B2C54267
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 1 May 2016 20:48:01 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from ozlabs.org (ozlabs.org [103.22.144.67])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D9B3EAA
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 1 May 2016 20:48:00 +0000 (UTC)
Received: by ozlabs.org (Postfix, from userid 1011)
id 3qyfdp2HWbz9t60; Mon, 2 May 2016 06:47:58 +1000 (AEST)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Rune =?utf-8?Q?Kj=C3=A6r?= Svendsen <runesvend@gmail.com>, Bitcoin
<bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <CAH2=CKxummve0yyCO6Tj9S3be6bLy0K4V1JatqAOVBCci5jobQ@mail.gmail.com>
References: <CAH2=CKxummve0yyCO6Tj9S3be6bLy0K4V1JatqAOVBCci5jobQ@mail.gmail.com>
User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1
(x86_64-pc-linux-gnu)
Date: Sun, 01 May 2016 13:46:20 +0930
Message-ID: <87oa8q5s6j.fsf@rustcorp.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, DATE_IN_PAST_12_24,
RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sun, 01 May 2016 21:26:37 +0000
Subject: Re: [bitcoin-dev] Simple Bitcoin Payment Channel Protocol v0.1
draft (request for comments)
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: Sun, 01 May 2016 20:48:01 -0000
Rune Kj=C3=A6r Svendsen via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> writes:
> Dear list
>
> I've spent the past couple of months developing a simple protocol for
> working with payment channels. I've written up a specification of how
> it operates, in an attempt to standardize the operations of opening,
> paying and closing.
Hi!
CHECKLOCKTIMEVERIFY [...] allows payment channel
setup to be risk free [...] something that was
not the case before, when the refund Bitcoin transaction
depended on another, unconfirmed Bitcoin transaction. Building
on unconfirmed transactions is currently not safe in Bitcoin
With Segregated Witness, this is now safe. With that expected soon, I'd
encourage you to take advantage of it.
Cheers,
Rusty.
|
