From: "Wladimir J. van der Laan" <laanwj@gmail•com>
To: Monarch <monarch@cock•li>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] push tx fuzzing
Date: Tue, 1 Sep 2015 20:03:34 +0200 [thread overview]
Message-ID: <20150901180333.GA3914@amethyst.visucore.com> (raw)
In-Reply-To: <e5c1d53a1387dce141d30c9eee6ee2ce@cock.li>
On Tue, Sep 01, 2015 at 04:59:15PM +0000, Monarch via bitcoin-dev wrote:
> which uses Bitcoin Core for validation. If they aren't validating
> transactions before broadcast they won't make it more than a single
> hop through the P2P the network so they are of minimum concern.
blockchain.info had some problems here for a while. They were not using a full validating node underneath:
- Signatures were not verified properly. This resulted in some panic when it looked like (on their site) a massive number of very old coins were being spent.
- They were relaying loose coinbase transactions. This caused them to be instantly banned from nodes they were connected to.
So there's certainly some scope for fun with fuzzing those APIs.
Wladimir
next prev parent reply other threads:[~2015-09-01 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 15:50 Kristov Atlas
2015-09-01 16:59 ` Monarch
2015-09-01 18:03 ` Wladimir J. van der Laan [this message]
2015-09-01 18:22 ` Manuel Aráoz
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=20150901180333.GA3914@amethyst.visucore.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=monarch@cock$(echo .)li \
/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