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 1Z5syx-00032p-VR for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 09:53:07 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.218.43 as permitted sender) client-ip=209.85.218.43; envelope-from=benjamin.l.cordes@gmail.com; helo=mail-oi0-f43.google.com; Received: from mail-oi0-f43.google.com ([209.85.218.43]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z5syw-0004m0-VL for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 09:53:07 +0000 Received: by oigx81 with SMTP id x81so76425178oig.1 for ; Fri, 19 Jun 2015 02:53:01 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.37.166 with SMTP id z6mr12977861oej.63.1434707581599; Fri, 19 Jun 2015 02:53:01 -0700 (PDT) Received: by 10.202.87.197 with HTTP; Fri, 19 Jun 2015 02:53:01 -0700 (PDT) In-Reply-To: References: <55828737.6000007@riseup.net> <55831CAB.2080303@jrn.me.uk> <1867667.WXWC1C9quc@crushinator> Date: Fri, 19 Jun 2015 11:53:01 +0200 Message-ID: From: Benjamin To: Mike Hearn Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.5 (-) 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 (benjamin.l.cordes[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Z5syw-0004m0-VL 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 09:53:08 -0000 Yeah, but increasing block-size is not a longterm solution. Necessary higher fees are a logical consequence of lower subsidies. Bitcoin was basically free to use at the beginning because miners got paid with new coins at the expense of those who already hold coins. Eventually there needs to be a mechanism which matches supply and demand. On Fri, Jun 19, 2015 at 11:37 AM, Mike Hearn wrote: >> Or alternatively, fix the reasons why users would have negative >> experiences with full blocks > > > It's impossible, Mark. By definition if Bitcoin does not have sufficient > capacity for everyone's transactions, some users who were using it will be > kicked out to make way for the others. Whether that happens in some kind of > stable organised way or (as with the current code) a fairly chaotic way > doesn't change the fundamental truth: some users will find their bitcoin > savings have become uneconomic to spend. > > Here's a recent user complaint that provides a preview of coming > attractions: > > https://www.reddit.com/r/Bitcoin/comments/39r3bi/breadwallet_asking_me_to_pay_over_10_network_fee/ > >> Hello, I'm just trying to send my small Sarutobi-tips stash (12,159 bits) >> onto a paper wallet. When I try to send it, a window pops up stating >> "insufficient funds for bitcoin network fee, reduce payment amount by 1,389 >> bits?" This would be a fee of $0.32 to send my $2.82, leaving me with $2.50. > > > These sorts of complaints will get more frequent and more extreme in the > coming months. I realise that nobody at Blockstream is in the position of > running an end user facing service, but many of us are .... and we will be > the ones that face the full anger of ordinary users as Bitcoin hits the > wall. > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >