summaryrefslogtreecommitdiff
path: root/72/7982dcee1151fc542ef155f90aca3fdae8ecf5
blob: 0328e38797a7d77962a49230e35c5f053e1e2860 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
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 <gmaxwell@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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: <CANEZrP3w+AiTXmv9Wb3Zi5yyFmGPk82-ysVo4_DVvtg8HHBCdQ@mail.gmail.com>
	<4FDB6946.2020400@justmoon.de>
	<CAErK2CgODFY7HMC-WZRAmts-6eOE074Tz4nX5Nr6EvB8o-QWJA@mail.gmail.com>
	<1339785500.74108.YahooMailNeo@web121006.mail.ne1.yahoo.com>
	<CAAS2fgSVbYFkkhP_0Ny5ULB-DJKN-3hZLkqWukrGL80-UenMwQ@mail.gmail.com>
	<1339786247.64852.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Date: Fri, 15 Jun 2012 14:55:52 -0400
Message-ID: <CAAS2fgQEFgLOEkSSTpn5OFuwa+AYA3LajTD-MqJ83rEPCW4u-Q@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
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"
	<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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 18:55:58 -0000

On Fri, Jun 15, 2012 at 2:50 PM, Amir Taaki <zgenjix@yahoo.com> 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.