public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail•com>
To: naman naman <namanhd@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>,
	Vocatus Gate <vocatus.gate@gmail•com>
Subject: Re: [Bitcoin-development] MtGox blames bitcoin
Date: Tue, 11 Feb 2014 12:49:49 -0800	[thread overview]
Message-ID: <CAAS2fgS5=-=6Ws0ofWsyKNHLYQop71kOjBCtF6TUMOmVgHtU_g@mail.gmail.com> (raw)
In-Reply-To: <CA+SxJWBM0USWETNeDh-oRgOfrU64GiPbL_Qt5hrFN53C42yNxg@mail.gmail.com>

On Tue, Feb 11, 2014 at 12:42 PM, naman naman <namanhd@gmail•com> wrote:
> I was talking about a DOS attack in
> https://bitcointalk.org/index.php?topic=458608.0 (ofcourse only applicable
> to entitys doing the tracking with txids).
>
> Amazing how I did not get a response from any of the devs (except Greg's
> response
> https://bitcointalk.org/index.php?topic=458608.msg5063789#msg5063789 but
> that too was short and not concerning the attack scenario plausibiity as I
> replied to him).

Try paying a consultant if your ego demands that you have a technical
expert to entertain your musing with immediate response.

My response was absolutely relevant.

If you reissue a transaction without respending the prior transactions
coins, you will end up double paying. Only spending the inputs in
question can prevent the prior transaction (itself or in other form)
from going through.

Once you respend the inputs there is no risk of actually losing funds
due to an issue regardless of how you track coins in your higher level
application.



  reply	other threads:[~2014-02-11 20:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 11:28 Drak
2014-02-10 11:54 ` sickpig
2014-02-10 12:25 ` Gregory Maxwell
2014-02-10 14:40 ` Isidor Zeuner
2014-02-10 16:30   ` Troy Benjegerdes
2014-02-10 16:45     ` Gregory Maxwell
2014-02-10 18:25       ` Troy Benjegerdes
2014-02-10 18:45         ` Jameson Lopp
2014-02-10 18:53           ` Gavin Andresen
2014-02-10 19:07           ` Troy Benjegerdes
2014-02-10 19:23             ` Peter Todd
2014-02-10 19:30               ` naman naman
2014-02-10 19:40                 ` Peter Todd
     [not found]                   ` <52F9377D.9010405@gmail.com>
2014-02-11 20:42                     ` naman naman
2014-02-11 20:49                       ` Gregory Maxwell [this message]
2014-02-11 20:56                         ` naman naman
2014-02-13 12:20                           ` naman naman
2014-02-10 16:49   ` Drak

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='CAAS2fgS5=-=6Ws0ofWsyKNHLYQop71kOjBCtF6TUMOmVgHtU_g@mail.gmail.com' \
    --to=gmaxwell@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=namanhd@gmail$(echo .)com \
    --cc=vocatus.gate@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