From: Rusty Russell <rusty@rustcorp•com.au>
To: "Rune Kjær Svendsen" <runesvend@gmail•com>,
Bitcoin <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Simple Bitcoin Payment Channel Protocol v0.1 draft (request for comments)
Date: Sun, 01 May 2016 13:46:20 +0930 [thread overview]
Message-ID: <87oa8q5s6j.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAH2=CKxummve0yyCO6Tj9S3be6bLy0K4V1JatqAOVBCci5jobQ@mail.gmail.com>
Rune Kjær 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.
prev parent reply other threads:[~2016-05-01 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 14:03 Rune Kjær Svendsen
2016-05-01 4:16 ` Rusty Russell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa8q5s6j.fsf@rustcorp.com.au \
--to=rusty@rustcorp$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=runesvend@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox