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 <luke@dashjr.org>) id 1Z3Y8D-0003c9-QH
	for bitcoin-development@lists.sourceforge.net;
	Fri, 12 Jun 2015 23:13:01 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of dashjr.org
	designates 85.234.147.28 as permitted sender)
	client-ip=85.234.147.28; envelope-from=luke@dashjr.org;
	helo=zinan.dashjr.org; 
Received: from 85-234-147-28.static.as29550.net ([85.234.147.28]
	helo=zinan.dashjr.org)
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1Z3Y8C-0006u9-Jy for bitcoin-development@lists.sourceforge.net;
	Fri, 12 Jun 2015 23:13:01 +0000
Received: from ishibashi.localnet (unknown
	[IPv6:2001:470:5:265:61b6:56a6:b03d:28d6])
	(Authenticated sender: luke-jr)
	by zinan.dashjr.org (Postfix) with ESMTPSA id 4E5F51083688;
	Fri, 12 Jun 2015 23:11:45 +0000 (UTC)
X-Hashcash: 1:25:150612:bitcoin-development@lists.sourceforge.net::udOi+/rGD8LDpEc=:amxZj
X-Hashcash: 1:25:150612:vincent.truong@procabiak.com::qTncfmSgbu60wEEV:/fIM
X-Hashcash: 1:25:150612:elombrozo@gmail.com::IDdyOk+Ss82jgnxp:bd4uS
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 12 Jun 2015 23:11:43 +0000
User-Agent: KMail/1.13.7 (Linux/3.14.41-gentoo; KDE/4.14.3; x86_64; ; )
References: <20150612181153.GB19199@muck>
	<CABr1YTd0wcOC8+KSPCPHrx5Ob4nY3azed46gS+nR_NzmxDiTzw@mail.gmail.com>
	<CACrzPemekkQdn5awnb9tBc9uWs12KLHQAdqu=4zAtjn=O-kkaw@mail.gmail.com>
In-Reply-To: <CACrzPemekkQdn5awnb9tBc9uWs12KLHQAdqu=4zAtjn=O-kkaw@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201506122311.44549.luke@dashjr.org>
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.0 TVD_RCVD_IP            Message was received from an IP address
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1Z3Y8C-0006u9-Jy
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: <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, 12 Jun 2015 23:13:01 -0000

On Friday, June 12, 2015 11:01:02 PM Vincent Truong wrote:
> RE: miner economics
> Miners who have an agenda can forego fees to achieve it and create their
> own txns if it is completely txn/user driven. It is better to just count
> miners votes and let the user votes be their backing.

Just simplify this? Allow a miner to have their block counted as <max possible 
votes> votes for X provided not a single transaction they include votes 
against it. Then miners can explicitly forego the fees of opposing 
transactions without having to bloat blocks.

Luke