Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z5vNs-0001cT-8x for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 12:27:00 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of hotmail.com designates 65.55.111.85 as permitted sender) client-ip=65.55.111.85; envelope-from=slashdevnull@hotmail.com; helo=BLU004-OMC2S10.hotmail.com; Received: from blu004-omc2s10.hotmail.com ([65.55.111.85]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Z5vNr-0001cB-6E for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 12:27:00 +0000 Received: from BLU437-SMTP99 ([65.55.111.72]) by BLU004-OMC2S10.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Fri, 19 Jun 2015 05:26:53 -0700 X-TMN: [Cs47ceYg0+vg0bqPOD0E8qjF2vKz6YWw] X-Originating-Email: [slashdevnull@hotmail.com] Message-ID: User-Agent: Microsoft-MacOutlook/14.4.9.150325 Date: Fri, 19 Jun 2015 19:26:45 +0700 From: GC To: Jorge =?ISO-8859-1?B?VGlt824=?= , Mike Hearn Thread-Topic: [Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers References: <55828737.6000007@riseup.net> <55831CAB.2080303@jrn.me.uk> <1867667.WXWC1C9quc@crushinator> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 19 Jun 2015 12:26:53.0208 (UTC) FILETIME=[394A2180:01D0AA8B] X-Spam-Score: -1.8 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (slashdevnull[at]hotmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [65.55.111.85 listed in list.dnswl.org] X-Headers-End: 1Z5vNr-0001cB-6E Cc: Bitcoin Development , Gavin Andresen Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2015 12:27:00 -0000 >When is the right time to allow space pressure to rise that ratio? >When the subsidy is at 1.5625, for example, it may be too late to I don=B9t believe we have to decide, the miners will do that and are doing that already. >start a non-catastrophic transition from subsidies to fees. >I don't claim to know that, but it's something that worries me. >No matter how many people say "that's too far away in the future to >worry about it", I still worry about it and I'm sure more people do. >What if "when it's time to care about it" we discover that we should >have started to do things about it long ago to minimize the risks of >this transition? Hmmm. What should be the price of an email? How much should DARPA have charged for using TCP/IP? I see a lot of well-paid, first-world technologists arguing for commercial returns on a nacent protocol which could could offer benefits to the unbanked. Is that really the vision: to (re)build a de-centralized Paypal with slightly cheaper fees and cool hooks into off-chain commercial systems providing profits for the already rich? >-------------------------------------------------------------------------- >---- >_______________________________________________ >Bitcoin-development mailing list >Bitcoin-development@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/bitcoin-development