From: Gregory Maxwell <gmaxwell@gmail•com>
To: theymos <theymos@mm•st>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] From the forums: one-confirmation attack
Date: Thu, 18 Aug 2011 13:27:29 -0400 [thread overview]
Message-ID: <CAAS2fgRxNiGYETKJJ-o=z=ZwBMR5Sa=yF54AXeV=VgP-bsTT8g@mail.gmail.com> (raw)
In-Reply-To: <1313686076.6324.140258131139585@webmail.messagingengine.com>
On Thu, Aug 18, 2011 at 12:47 PM, theymos <theymos@mm•st> wrote:
> To make this more difficult, nodes that receive new transactions via
> blocks should relay the new transactions as if they had received them
> normally. Then the double-spend transaction will be rejected by most of
> the network because the other version is already widely-known.
Not that helpful. In that attack pattern the attacker can release the
block and the conflicting transaction at the same time (to different
nodes, of course). They can also inject the conflicting transaction
into many places in the network at once.
prev parent reply other threads:[~2011-08-18 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 14:00 Gavin Andresen
2011-08-18 15:36 ` Joel Joonatan Kaartinen
2011-08-18 15:52 ` Mike Hearn
2011-08-18 16:16 ` Gavin Andresen
2011-08-18 16:46 ` Gregory Maxwell
2011-08-18 17:36 ` Gavin Andresen
2011-08-18 16:47 ` theymos
2011-08-18 17:27 ` Gregory Maxwell [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='CAAS2fgRxNiGYETKJJ-o=z=ZwBMR5Sa=yF54AXeV=VgP-bsTT8g@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=theymos@mm$(echo .)st \
/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