public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Tom Harding <tomh@thinlink.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] IMPULSE: Instant Payments using the Bitcoin protocol
Date: Thu, 22 Jan 2015 11:29:24 -0500	[thread overview]
Message-ID: <CAJHLa0PX31xF6rFugW3z1x-xXmzZGn47EnQESSggJpQ=7my7DQ@mail.gmail.com> (raw)
In-Reply-To: <54C114FE.4070308@thinlink.com>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

The user experience is significantly more secure than today.

Presumably the future supports many payment facilitators, including m-of-n
oracles, and this is perfectly compatible with that.


On Thu, Jan 22, 2015 at 10:19 AM, Tom Harding <tomh@thinlink.com> wrote:

> On 1/17/2015 12:45 PM, Rune Kjær Svendsen wrote:
> > PDF: http://impulse.is/impulse.pdf
> >
> > I'd love to hear this list's thoughts.
> >
>
> Will success be defined by "BitPay Payment Channels Accepted Here" signs
> appearing in shop windows?
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>



-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

[-- Attachment #2: Type: text/html, Size: 2048 bytes --]

  reply	other threads:[~2015-01-22 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17 20:45 [Bitcoin-development] IMPULSE: Instant Payments using the Bitcoin protocol Rune Kjær Svendsen
2015-01-22 15:19 ` Tom Harding
2015-01-22 16:29   ` Jeff Garzik [this message]
2015-01-22 16:36 ` Justus Ranvier

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='CAJHLa0PX31xF6rFugW3z1x-xXmzZGn47EnQESSggJpQ=7my7DQ@mail.gmail.com' \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=tomh@thinlink.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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