Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pete@petertodd.org>) id 1YrYCa-0004oK-GZ
	for bitcoin-development@lists.sourceforge.net;
	Sun, 10 May 2015 20:51:56 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.112 as permitted sender)
	client-ip=62.13.149.112; envelope-from=pete@petertodd.org;
	helo=outmail149112.authsmtp.co.uk; 
Received: from outmail149112.authsmtp.co.uk ([62.13.149.112])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1YrYCY-0004KQ-By for bitcoin-development@lists.sourceforge.net;
	Sun, 10 May 2015 20:51:56 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
	by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t4AKpj87035891;
	Sun, 10 May 2015 21:51:45 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
	[75.119.251.161]) (authenticated bits=128)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t4AKpg20094215
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Sun, 10 May 2015 21:51:45 +0100 (BST)
Date: Sun, 10 May 2015 16:51:41 -0400
From: Peter Todd <pete@petertodd.org>
To: Sergio Lerner <sergiolerner@certimix.com>
Message-ID: <20150510205141.GA7465@savin.petertodd.org>
References: <554FC36C.80402@certimix.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl"
Content-Disposition: inline
In-Reply-To: <554FC36C.80402@certimix.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 5ea2acc2-f756-11e4-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aAdMdwIUFVQNAgsB AmMbWVVeVVx7XWY7 bA9PbARUfEhLXhtr
	VklWR1pVCwQmRRhw fV5JUBlyfgFEeXs+ bUJgWj5eCRV4JBUu
	QFMCEmgAeGZhPWQC AkNRcR5UcAFPdx8U a1UrBXRDAzANdhES
	HhM4ODE3eDlSNilR RRkIIFQOdA4iViE1 VlgeGn0kB0AMWyh7
	JlQoJ1NUGU8LMUgu eVY/VFRQLB4OCgpD AyMFCWdTI14KRGIw
	DBFXFUofFTxBCWcG WkRzY3fQ
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
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 SPF_PASS               SPF: sender matches SPF record
	-0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YrYCY-0004KQ-By
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A way to create a fee market even without
 a block size limit (2013)
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: Sun, 10 May 2015 20:51:56 -0000


--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 10, 2015 at 05:45:32PM -0300, Sergio Lerner wrote:
> Two years ago I presented a new way to create a fee market that does not
> depend on the block chain limit.

<snip>

> Solution: Require that the set of fees collected in a block has a
> dispersion below a threshold. Use, for example, the Coefficient of
> Variation (http://en.wikipedia.org/wiki/Coefficient_of_variation). If
> the CoVar is higher than a fixed threshold, the block is considered inval=
id.

It's not possible to create consensus rules enforcing anything about
fees because it's trivial to pay miners out of band.

For instance, you can pay transaction fees by including anyone-can-spend
outputs in your transactions. The miner creating the block then simply
adds a transaction at the end of their block collecting all the
anyone-can-spend outputs. Equally, if you try to prohibit that - e.g. by
preventing respending of funds in the same block - they can simply
publish fee addresses and have people put individual outputs for those
addresses in their transactions. (IIRC Eligius gave people the option to
pay fees that way for awhile)

--=20
'peter'[:-1]@petertodd.org
00000000000000000fa57b40dc86a61d35aaf9241c86f047ef6f4bab8f13dfb7

--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJVT8TZXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwYmRmMTI0NTczZjVkMzk3NjRhN2IyYjkwNjkxY2M4OTRk
ODIyNzhlYWRmZGNkNjAvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkft0uwgAk6tFybcXvhAvYoAbIJxd9gA/
v4OqvIa4A3TiE0sv5rsB0ZDWT/5FW5agVucB9Kob4siLfbu3FFTzuCGZnH3wYUE6
0hDWwSxM15BQnJXCugkDeQjz8GALJAq+bWZCDVruuuJOlu+0p93u8Vz/okhKZuvZ
HkYkqrZpXdE2ZNxM7KPduDXU4jZx5L9VmEdjZFfVujfK8mEBYDG3ZEUaltmHuUvj
BEtOLBqk8hXQAwtMl1zoF4/XK/VWZs1zDNW+92Z9op/601bZk8zPJGJXH4jRY1bD
28pgFfry2DZuHGg+Np1U9dYHLDCCk0DscHbg+6s19swqdLS5Ap9uqxy8Prs2sA==
=rVkL
-----END PGP SIGNATURE-----

--BXVAT5kNtrzKuDFl--