From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B2C54267 for ; 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 ; 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 To: Rune =?utf-8?Q?Kj=C3=A6r?= Svendsen , Bitcoin In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2016 20:48:01 -0000 Rune Kj=C3=A6r Svendsen via bitcoin-dev 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.