From: Jeff Garzik <jgarzik@bitpay•com>
To: Arthur Gervais <arthur.gervais@inf•ethz.ch>
Cc: Ghassan Karame <ghassan@karame•org>,
bitcoin-development@lists•sourceforge.net,
Hubert Ritzdorf <rihubert@inf•ethz.ch>
Subject: Re: [Bitcoin-development] Double-Spending Fast Payments in Bitcoin due to Client versions 0.8.1
Date: Thu, 27 Jun 2013 12:16:04 -0400 [thread overview]
Message-ID: <CAJHLa0MVrQN6hyuAsYNRJ2CV6fsPnAbRDSUQH+n6jfKdMiFaLQ@mail.gmail.com> (raw)
In-Reply-To: <51CC6259.3060003@inf.ethz.ch>
On Thu, Jun 27, 2013 at 12:03 PM, Arthur Gervais
<arthur.gervais@inf•ethz.ch> wrote:
> Our only intention is to raise the awareness for merchants who have to
> accept zero-confirmation transactions. They should be aware of the
> signature encoding difference between Bitcoin versions and the possible
> consequences.
Certainly. Though given current P2P network node version
distributions, it is increasing difficult to relay the older version
of transaction, and will only become more so in the future.
It also remains the case that merchants who accept zero confirmation
transactions are likely already aware of the risk level, and make a
business decision. One can see tiny digital downloads often at zero
confirmation, but rarely a Porsche or house or bitcoin exchange
deposit.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
prev parent reply other threads:[~2013-06-27 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 10:23 Arthur Gervais
2013-06-27 11:04 ` Gregory Maxwell
2013-06-27 16:03 ` Arthur Gervais
2013-06-27 16:13 ` Gregory Maxwell
2013-06-27 16:16 ` Jeff Garzik [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=CAJHLa0MVrQN6hyuAsYNRJ2CV6fsPnAbRDSUQH+n6jfKdMiFaLQ@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=arthur.gervais@inf$(echo .)ethz.ch \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=ghassan@karame$(echo .)org \
--cc=rihubert@inf$(echo .)ethz.ch \
/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