public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Dave Scotese <dscotese@litmocracy.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis
Date: Fri, 24 Jul 2015 19:23:00 -0700	[thread overview]
Message-ID: <CAGLBAhdggPPnxLgp+xQPWGtK1KA_QZt7eug2votak4in2DrwJA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]

Incentivize investigations for public consumption.  The people on this list
are the ones who probably care the most.

When I looked up that IP address, the Whois info names "OVH" and "Octave
Klaba" (who founded OVH, according to Wikipedia) as the owner.  "
blockchain.info" appears in the HTML header as retrieved by the
"Anti-Hacker Alliance" (
http://anti-hacker-alliance.com/index.php?details=37.187.136.15).
Blockchain.info itself returns IP addresses managed by CloudFlare whenever
I try it.

On Fri, Jul 24, 2015 at 2:12 PM, Slurms MacKenzie via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> They do not run anything but BitcoinJ (evidenced by them blindly following
> invalid chains), so no proper consensus checking going on here at all.
> Connected to my nodes is a bad peer (doesn’t relay inventory but downloads
> everything) from 37.187.136.15, with the user agent
> /BitcoinJ:0.12SNAPHOT/Satoshi:0.2.0/ which is owned by blockchain.info.
> You can also submit an invalid transaction through their /pushtx interface
> and get a mixture of noise and BitcoinJ error messages out of it as well.
>
> If even the people who have to their claim hundreds of thousands of
> wallets are relying on their security don’t bother running even a single
> node to sanity check against, who are we really going to expect people to
> in the future if the load goes 8x, 16x, 32x higher? Like CoinBase and
> others, these are the companies which are claimed will be the ones
> supporting the network with ludicrous sized blocks because they have a
> financial incentive to.
>
> Well, they don't even do it now when it could be achieved with a $5 VPS.
>
>
> > Sent: Friday, July 24, 2015 at 8:43 PM
> > From: "Peter Todd via bitcoin-dev" <
> bitcoin-dev@lists.linuxfoundation.org>
> > To: "Thomas Zander" <thomas@thomaszander.se>
> > Cc: bitcoin-dev@lists.linuxfoundation.org
> > Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing"
> Analysis
> > We can test the fact that blockchain.info's wallet and block explorer
> > has behaved in a way consistent with not running a full node - they have
> > shown invalid data that any full node would reject on multiple
> > occasions, most recently invalid confirmations during the BIP66 fork.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 3602 bytes --]

             reply	other threads:[~2015-07-25  2:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25  2:23 Dave Scotese [this message]
2015-07-25 11:19 ` [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis Slurms MacKenzie
  -- strict thread matches above, loose matches on Subject: below --
2015-07-24  2:57 Dave Scotese
2015-07-24  3:37 ` Slurms MacKenzie
2015-07-24 11:38   ` Mike Hearn
2015-07-24 14:09     ` Adam Back
2015-07-24 15:22       ` Simon Liu
2015-07-24 17:40       ` Peter Todd
2015-07-24 20:28         ` Eric Lombrozo
2015-07-24 20:31           ` Eric Lombrozo
2015-07-24 15:08     ` Dave Scotese
2015-07-24 13:39   ` Thomas Zander
2015-07-24 17:43     ` Peter Todd
2015-07-24 20:23       ` Eric Lombrozo
2015-07-24 21:12       ` Slurms MacKenzie
2015-07-24 15:40 ` Milly Bitcoin

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=CAGLBAhdggPPnxLgp+xQPWGtK1KA_QZt7eug2votak4in2DrwJA@mail.gmail.com \
    --to=dscotese@litmocracy.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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