--[remove this line and above]-- On Thu, 7 May 2015, Gregory Maxwell wrote:
> Date: Thu, 7 May 2015 00:37:54 +0000 > From: Gregory Maxwell <gmaxw...@gmail.com> > To: Matt Corallo <bitcoin-l...@bluematt.me> > Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> > Subject: Re: [Bitcoin-development] Block Size Increase > > Thanks Matt; I was actually really confused by this sudden push with > not a word here or on Github--so much so that I responded on Reddit to > people pointing to commits in Gavin's personal repository saying they > were reading too much into it. I saw this. I was also pointing this out to the people who were asking me. A commit to a personal repository does not at first seem more than experimental. sipa commits weird/neat things to private branches all the time, after all. > to share behavior. In the case of mining, we're trying to optimize the > social good of POW security. (But the analogy applies in other ways > too: About the only argument IMO in favour of block size increases is to assume that making more room in a block will make it attractive to use for more people at some point in the future: increasing transaction velocity, increasing economy size, increasing value overall. > increases to the chain side are largely an externality; miners enjoy > the > benefits, everyone else takes the costs--either in reduced security or > higher node operating else.) Who else but miners and pool operators will run full nodes when full nodes are being shut down because they are too large and unwieldy to maintain? It is already so that casual users refuse to run full nodes. This fact is indisputable. The only question remaining is, "Do we care?" Arguments against users who feel that the dataset is too large to run a full node, full-time, start from a premise that these users are a static and irrelevant fraction. Is this even true? "Do we care?" I do. I will shortly only be able to run half the nodes I currently do thanks to the growth of the blockchain at its current rate. > One potential argument is that maybe miners would be _regulated_ to > behave correctly. But this would require undermining the openness of > the > system--where anyone can mine anonymously--in order to enforce > behavior, > and that same enforcement mechanism would leave a political level to > impose additional rules that violate the extra properties of the > system. I would refuse to mine under such a regulated regime; moreover, I would enjoy forking away from this, and, I suspect, the only miners who remain would be those whose ultimate motivations do not coincide with the users. That is, the set of miners who are users, and the set of users who are miners, would be wholly non-intersecting. > So far the mining ecosystem has become incredibly centralized over > time. This is unfortunate but true. > of the regular contributors to Bitcoin Core do. Many participants > have never mined or only did back in 2010/2011... we've basically > ignored the mining ecosystem, and this has had devastating effects, > causing a latent undermining of the security model: hacking a dozen or > so computers--operated under totally unknown and probably not strong > security policies--could compromise the network at least at the tip... The explicit form of the block dictated by the reference client and agreed-to by the people who were sold on bitcoin near the beginning (myself included) was explicitly the notion that the rules were static; that the nature of transaction foundations and the subsidies would not be altered. Here we have a hardfork being contemplated which is not only controversial, but does not even address some of the highest-utility and most-requested features in peoples' hardfork wishlists. The fact that mining has effectively been centralized directly implies that destabilizing changes that some well-heeled (and thus theoretically capable, at least) people have explicitly begun plans to fork the blockchain about will have an unknown, and completely unforeseen combined effect. We can pretend that, "If merchants and miners and exchanges go along, then who else matters," but the reality is that the value in bitcoin exists because *people* use it for real transactions: Not miners, whose profits are parasitically fractionally based on the quality and strength of the bitcoin economy as a whole; not exchanges who lubricate transactions in service to the economy; not even today's merchants whose primary means of accepting bitcoin seems to be to convert them instantly to fiat and not participate meaningfully in the economy at all; not enriched felons; but actual users themselves. > Rightfully we should be regarding this an an emergency, and probably > should have been have since 2011. There are two ways to look at it, assuming that the blocksize change increases bitcoin's value to people after all: mining centralization will be corrected; or, mining centralization will not be corrected. I would argue that rapidly increasing profitability at this point will exacerbate the mining centralization problem, and in much the same way as when people were throwing money and unknowingly funding the massive frauds of the current cabals when bitcoin's exchange-driven rise to $1200 was first realized. Thus, even if the premise were true, what will a blocksize increase achieve given mining centralization itself is a bigger systemic risk? > Hardfork changes should only be made if they're almost completely > uncontroversial--where virtually everyone can look at the available > data > and say "yea, that isn't undermining my property rights or future use > of Bitcoin; it's no big deal". The recent "revelation" that there are masses of paid trolls on popular forum sites like reddit who supposedly don't even know who is hiring them, and the anger of more vociferous commenters in general, does not invalidate the relevance of every non-"industry" voice. I think elevating the discussion away from the users does the system and the development process as a whole quite an injustice. > I'm curious as to what discussions people have seen; e.g., are people > even here aware of these concerns? Are you aware of things like the > hashcash mediated dynamic blocksize limiting? I have seen most of these; or the ideas seem obvious based on their names. > About proposals like lightning network (instant transactions and > massive > scale, in exchange for some short term DOS risk if a counterparty opts > out)? Do people (other than Mike Hearn; I guess) think a future where > everyone depends on a small number of "Google scale" node operations > for > the system is actually okay? (I think not, and if so we're never going > to > agree--but it can be helpful to understand when a disagreement is > ideological). It is not okay. If the current mining cabals continue to exist, and flourish, and the developers make major changes that ignore this glaring elephant, then the decentralized promise of bitcoin will be put more at risk. signmessage 1DdcrjT9Yqb6U58wVMA2e7untFbz2rmZd4 "49786791f4d0a260689867ccdfb2cc5b8460984e335504444ade113d2768505c" G6NPl7Wklo9lcdgeVI2H2pexzgqD0KPHhI/wAe32DBm8m59Qf31j5d4tsx5drcql/8wPeIb0QGarr/o4VIOLLGE= --[remove this line and below]-- HHsTfiZ/S7+GNYRwws+QyAr+6/MgDz0Jyntl7CAvjhdfzbnwPorybQUXxRw3CE4DgYgAy1zLanE8H/5NK+l3UlE= ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
