Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Sfbgc-0005od-5V for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 18:55:58 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.174 as permitted sender) client-ip=209.85.216.174; envelope-from=gmaxwell@gmail.com; helo=mail-qc0-f174.google.com; Received: from mail-qc0-f174.google.com ([209.85.216.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Sfbgb-0002ic-KP for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 18:55:58 +0000 Received: by qcro28 with SMTP id o28so2104598qcr.33 for ; Fri, 15 Jun 2012 11:55:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.134.199 with SMTP id k7mr3623767qct.4.1339786552191; Fri, 15 Jun 2012 11:55:52 -0700 (PDT) Received: by 10.229.144.205 with HTTP; Fri, 15 Jun 2012 11:55:52 -0700 (PDT) In-Reply-To: <1339786247.64852.YahooMailNeo@web121006.mail.ne1.yahoo.com> References: <4FDB6946.2020400@justmoon.de> <1339785500.74108.YahooMailNeo@web121006.mail.ne1.yahoo.com> <1339786247.64852.YahooMailNeo@web121006.mail.ne1.yahoo.com> Date: Fri, 15 Jun 2012 14:55:52 -0400 Message-ID: From: Gregory Maxwell To: Amir Taaki Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 (gmaxwell[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: From: address is in the auto white-list X-Headers-End: 1Sfbgb-0002ic-KP Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Near-term scalability 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, 15 Jun 2012 18:55:58 -0000 On Fri, Jun 15, 2012 at 2:50 PM, Amir Taaki wrote: > Part of the problem is that Satoshi didn't totally anticipate the growth = of the network. The block reward (the subsidy) is too high, which is why tr= ansactions can afford to be so cheap. What would happen if blocks required = a cumulative fee of XN BTC for N transactions before being accepted? I would take the last block I solved and use it to write a transaction to nowhere which which gave all 50 BTC out in fee. This pays for as many transactions in the block as I like for any value of X you want to choose. You should read the bitcointalk forums more often: variants on that idea are frequently suggested and dismantled. There is a lot of noise there but also a lot of ideas and knowing what doesn't work is good too.