From: Gregory Maxwell <gmaxwell@gmail•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 09:13:58 -0700 [thread overview]
Message-ID: <CAAS2fgRkoY_vHXKyyh91Wfm0f_qW6d_FeKzO+mi-WpDRUxtsRw@mail.gmail.com> (raw)
In-Reply-To: <51CC6259.3060003@inf.ethz.ch>
On Thu, Jun 27, 2013 at 9:03 AM, Arthur Gervais
<arthur.gervais@inf•ethz.ch> wrote:
> affecting the same Bitcoin version. However we think it is
> complementary, since our reported problem has nothing to do with fees,
> dust, nor is it necessary to send the two double-spending transaction at
> the same time. In our setting, double-spending still works if the second
> transaction is sent after minutes (and the first transaction has not yet
> been included into a block).
It works just the same for dust based or any other criteria that makes
transactions non-standard— including the double spending working if
the second transaction is sent minutes after. Exactly the same code is
executed and the same behavior observed for any case of a non-standard
transaction being used to achieve inconsistent forwarding.
> Our only intention is to raise the awareness for merchants who have to
> accept zero-confirmation transactions.
That is great and I'm certainly glad to see people doing that.
Though take care it that your focus on signature encoding differences
doesn't create a misunderstanding. This isn't only an issue with these
particular versions: There is always mining and relay behavior
inhomogeneity in the network. The level of inhomogeneity changes over
time— I believe its greatest when new reference client software that
changes IsStandard but it is never zero as there are large miners with
customized acceptance rules (also mempool state also creates
inhomogeneity). The greater inhomogeneity results in higher success
rates which may be important since some service could conceivable only
be profitable exploited with a high enough success rate.
next prev parent reply other threads:[~2013-06-27 16:14 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 [this message]
2013-06-27 16:16 ` Jeff Garzik
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=CAAS2fgRkoY_vHXKyyh91Wfm0f_qW6d_FeKzO+mi-WpDRUxtsRw@mail.gmail.com \
--to=gmaxwell@gmail$(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