From: Pieter Wuille <pieter.wuille@gmail•com>
To: "Rebroad (sourceforge)" <rebroad+sourceforge.net@gmail•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Potential network split when individual tx used as coinbase?
Date: Sat, 5 May 2012 13:40:35 +0200 [thread overview]
Message-ID: <20120505114034.GA24827@vps7135.xlshosting.net> (raw)
In-Reply-To: <CAFBxzAADB9PvbzQpH8R0CSH5yTy-9bG8Bf=gRjDnbPDdWXsGsw@mail.gmail.com>
On Sat, May 05, 2012 at 09:31:39AM +0100, Rebroad (sourceforge) wrote:
> Hi,
> >
> >
> Looking at:
> https://github.com/bitcoin/bitcoin/commit/3e52aaf2121d597ab1ed012b65e37f9cb5f2754e#src/main.cpp-P52
>
> It appears that 8 months ago the code was changed to DoS(100) nodes sending
> on txs that use individual txs as the coinbase. Does this mean txs that are
> 0 confirmed?
>
> Or have I misread the code?
I think so, see my comment there.
--
Pieter
prev parent reply other threads:[~2012-05-05 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFBxzADBoEU9ncCxsHg7_tMz_WmAnhDrh_m8kWw4Nb5FykjfEg@mail.gmail.com>
2012-05-05 8:31 ` Rebroad (sourceforge)
2012-05-05 11:40 ` Pieter Wuille [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=20120505114034.GA24827@vps7135.xlshosting.net \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=rebroad+sourceforge.net@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