From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z3YJ3-0003xg-Sh for bitcoin-development@lists.sourceforge.net; Fri, 12 Jun 2015 23:24:13 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.196 as permitted sender) client-ip=209.85.214.196; envelope-from=gustafsonja@gmail.com; helo=mail-ob0-f196.google.com; Received: from mail-ob0-f196.google.com ([209.85.214.196]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z3YJ3-0007RZ-3D for bitcoin-development@lists.sourceforge.net; Fri, 12 Jun 2015 23:24:13 +0000 Received: by obcwm4 with SMTP id wm4so7579013obc.3 for ; Fri, 12 Jun 2015 16:24:07 -0700 (PDT) X-Received: by 10.202.95.198 with SMTP id t189mr13225038oib.105.1434151447703; Fri, 12 Jun 2015 16:24:07 -0700 (PDT) MIME-Version: 1.0 Sender: gustafsonja@gmail.com Received: by 10.202.194.68 with HTTP; Fri, 12 Jun 2015 16:23:37 -0700 (PDT) In-Reply-To: References: <20150612181153.GB19199@muck> <1466351.XXvDcu7nzO@crushinator> From: Aaron Gustafson Date: Fri, 12 Jun 2015 16:23:37 -0700 X-Google-Sender-Auth: ayNpRUiQXf_3lq_JIo8L0_4SolQ Message-ID: To: Eric Lombrozo Content-Type: multipart/alternative; boundary=001a113ccfa698350405185a67c3 X-Spam-Score: -0.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 (gustafsonja[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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 X-Headers-End: 1Z3YJ3-0007RZ-3D Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] User vote in blocksize through fees 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, 12 Jun 2015 23:24:13 -0000 --001a113ccfa698350405185a67c3 Content-Type: text/plain; charset=UTF-8 On Fri, Jun 12, 2015 at 1:04 PM, Eric Lombrozo wrote: > Miners currently only collect an almost negligible portion of their > revenue from fees. Then they shouldn't care about the block size limit, since an increase in block size (and thus in the number of txs they get fees from) will only increase their revenue "negligibly". --001a113ccfa698350405185a67c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Fri, Jun 12, 2015 at 1:04 PM, Eric Lombrozo <elombrozo@gmail.com&= gt; wrote:
Miners currently only c= ollect an almost negligible portion of their revenue from fees.

Then they shouldn't care about the block size limit, since a= n increase in block size (and thus in the number of txs they get fees from)= will only increase their revenue "negligibly".
--001a113ccfa698350405185a67c3--