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 23:11:33 +0000 [thread overview]
Message-ID: <em36157ae1-7c4b-488f-88d6-5a8df930ef0f@platinum> (raw)
In-Reply-To: <55FF3878.4060501@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:51:36 PM
Subject: Re: [bitcoin-dev] Scaling Bitcoin conference micro-report
>>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.
>
>It sounds more efficient but it is not clear to me that it would change
>the level of centralization of how the final decisions are made.
>
>One threat to Bintcoin involves incentive for companies to hire
>developers. The only reason is to change (or not change) Bitcoin Core
>so it is beneficial to their interests. I am not sure anything can be
>done about that risk but it needs to be understood and considered and
>not just ignored.
Core development process and decentralized dev/community consensus
building (in particular for consensus-critical changes) is at the top of
my priorities as issues right now...and one that I'd love to discuss
more in depth...but it probably deserves its own thread. The political
angle seems very difficult right now while the systems architecture
stuff seems a bit more tractable...and it seems that without
architectural changes it will be extremely hard to decentralize
development and easily bring large numbers of new developers in.
>
>>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.
>
>I assume that would mean fees that hike transaction fees and make
>Bitcoin more expensive?
>
Not necessarily. Right now we already pay around 3,600 bitcoins a day in
inflationary subsidies, very little of which goes to the majority of
critical infrastructure nodes and their operators. This is a problem
with the current protocol design, one we'll hopefully be able to fix.
Having more core infrastructure nodes doesn't need to raise costs per
transaction - but it will most likely require abandoning the current
approach of having three basic node classes: miners (which tend towards
centralized pools), full nodes (which must validate each of everyone's
transaction and in return get paid nothing), and thin clients (which
essentially amount to parasitic nodes that do not contribute any
resources back to the network and must be subsidized).
next prev parent reply other threads:[~2015-09-20 23:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 21:32 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
2015-09-20 22:51 ` Milly Bitcoin
2015-09-20 23:11 ` Eric Lombrozo [this message]
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=em36157ae1-7c4b-488f-88d6-5a8df930ef0f@platinum \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=milly@bitcoins$(echo .)info \
/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