From: "Eric Lombrozo" <elombrozo@gmail.com>
To: "Milly Bitcoin" <milly@bitcoins.info>,
bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Scaling Bitcoin conference micro-report
Date: Sun, 20 Sep 2015 22:21:55 +0000 [thread overview]
Message-ID: <eme6e53f4a-40c6-4b6f-8cf1-b2e8d9905e9d@platinum> (raw)
In-Reply-To: <55FF2CF8.2010408@bitcoins.info>
------ Original Message ------
From: "Milly Bitcoin via bitcoin-dev"
<bitcoin-dev@lists.linuxfoundation.org>
To: bitcoin-dev@lists.linuxfoundation.org
Sent: 9/20/2015 3:02:32 PM
Subject: Re: [bitcoin-dev] Scaling Bitcoin conference micro-report
>>Larger user base won't necessarily protect against governments if we
>>still have chokepoints they can go after.
>
>
>Bitcoin will always have chokepoints governments can go after. Hackers
>already targeted routers to divert mining traffic awhile back. Bitcoin
>traffic is easily seen and blocked by ISP's. It has already been
>pointed out that laws against merchants and exchanges cannot be
>defended against any other way than to have many people use the system.
Almost none of these merchants depend on Bitcoin in any significant way
for revenue...and that's likely to remain the case for a good while.
Merchants that have chosen to accept Bitcoin are typically using a
handful of payment processors, again...chokepoints. And almost none of
them are contributing any network resources back to Bitcoin.
Exchanges are indeed serious chokepoints. But increasing the number of
users will probably have relatively little effect on this unless we also
increase the number of exchanges and decentralize the exchanges. If all
we had to do is increase the number of users, the same argument could be
used to claim that banks would be less susceptible to governmental
crackdowns if they just had more account holders.
Exchange decentralization is indeed another thing we must work towards -
but that's probably beyond the scope of the more pressing issue which is
building consensus in Bitcoin development.
>(As a developer you, of course, did not mention the threat of having a
>tiny number of developers who have significant influence over Bitcoin.
>It always amazes me the endless discussion over miners centralization
>and almost zero discussion of developer decentralization.)
I've pointed out this weakness of Bitcoin *numerous* times. That I
failed to mention it here does not mean it hasn't been discussed
elsewhere. Some of us have also been actively working towards developing
a more modular, layered architecture and better implementations that
will afford greater decentralization in software development with less
need for critical code reviews, less pushback from downstream developers
who must continuously rebase, a better process for building consensus in
the community, and simpler app migration.
>
>
>Increasing the nodes by a factor of 2 or 3 or keeping the block size
>small to increase the diversity of miners by a few percent will have
>zero effect if those other government threats were to actually happen.
>
We need to increase the basic infrastructure nodes by a factor much
larger than 2 or 3...more like 100 or 1000...and it's entirely doable
with properly aligned incentives.
>Russ
>
>
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev@lists.linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-09-20 22:22 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 21:32 [bitcoin-dev] Scaling Bitcoin conference micro-report Jeff Garzik
2015-09-16 21:51 ` Matt Corallo
2015-09-18 5:55 ` Mark Friedenbach
2015-09-18 17:10 ` Dave Scotese
2015-09-18 17:28 ` Eric Lombrozo
2015-09-18 20:06 ` Matt Corallo
2015-09-18 22:33 ` Mike Hearn
2015-09-19 16:03 ` cipher anthem
2015-09-19 20:43 ` Mike Hearn
2015-09-19 1:47 ` Peter Todd
2015-09-19 6:06 ` NxtChg
2015-09-19 6:56 ` Eric Voskuil
2015-09-19 7:27 ` NxtChg
2015-09-19 7:39 ` Eric Voskuil
2015-09-19 7:57 ` NxtChg
2015-09-19 8:52 ` Eric Voskuil
2015-09-19 13:32 ` NxtChg
2015-09-19 20:57 ` Mike Hearn
2015-09-19 21:53 ` phm
2015-09-20 1:26 ` Dave Scotese
2015-09-20 2:18 ` Milly Bitcoin
2015-09-20 9:18 ` NxtChg
2015-09-20 9:25 ` Mike Hearn
2015-09-20 15:43 ` Mark Friedenbach
2015-09-20 16:21 ` NxtChg
2015-09-20 16:34 ` Milly Bitcoin
2015-09-20 20:23 ` Steven Pine
2015-09-20 20:54 ` Milly Bitcoin
2015-09-20 21:33 ` s7r
2015-09-20 21:45 ` Eric Lombrozo
2015-09-20 22:02 ` Milly Bitcoin
2015-09-20 22:21 ` Eric Lombrozo [this message]
2015-09-20 22:51 ` Milly Bitcoin
2015-09-20 23:11 ` Eric Lombrozo
2015-09-21 0:11 ` Dave Scotese
2015-09-21 5:04 ` Corey Haddad
2015-09-21 11:45 ` Milly Bitcoin
2015-09-21 8:48 ` NxtChg
2015-09-20 21:10 ` NxtChg
2015-09-20 21:13 ` Steven Pine
2015-09-20 21:34 ` Milly Bitcoin
2015-09-20 21:24 ` Milly Bitcoin
2015-09-20 21:16 ` Eric Lombrozo
2015-09-21 10:30 ` Mike Hearn
2015-09-18 22:15 ` [bitcoin-dev] Improving Blocksize Communication Through Markets Paul Sztorc
2015-09-20 11:41 ` Isidor Zeuner
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=eme6e53f4a-40c6-4b6f-8cf1-b2e8d9905e9d@platinum \
--to=elombrozo@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=milly@bitcoins.info \
/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