public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <hearn@vinumeris.com>
To: Slurms MacKenzie <slurms@gmx.us>
Cc: bitcoin-dev@lists.linuxfoundation.org, dscotese@litmocracy.com
Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis
Date: Fri, 24 Jul 2015 13:38:46 +0200	[thread overview]
Message-ID: <CA+w+GKS91NWB9ffysD4qEvAm+r1PswMePq6dirshbcZzpFg6Cg@mail.gmail.com> (raw)
In-Reply-To: <trinity-44986062-638d-4c20-a1f8-56a7c7cec648-1437709050654@3capp-mailcom-bs10>

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

>
> It's worth noting that even massive companies with $30M USD of funding
> don't run a single Bitcoin Core node


This has nothing to do with block sizes, and everything to do with Core not
directly providing the services businesses actually want.

The whole "node count is falling because of block sizes" is nothing more
than conjecture presented as fact. The existence of multiple companies who
could easily afford to do this but don't because they perceive it as
valueless should be a wakeup call there.

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

  reply	other threads:[~2015-07-24 11:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  2:57 [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis Dave Scotese
2015-07-24  3:37 ` Slurms MacKenzie
2015-07-24 11:38   ` Mike Hearn [this message]
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
2015-07-25  2:23 Dave Scotese
2015-07-25 11:19 ` Slurms MacKenzie

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=CA+w+GKS91NWB9ffysD4qEvAm+r1PswMePq6dirshbcZzpFg6Cg@mail.gmail.com \
    --to=hearn@vinumeris.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=dscotese@litmocracy.com \
    --cc=slurms@gmx.us \
    /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