Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <tamas@bitsofproof.com>) id 1VZkjG-0001NF-8e for bitcoin-development@lists.sourceforge.net; Fri, 25 Oct 2013 16:59:18 +0000 X-ACL-Warn: Received: from wp059.webpack.hosteurope.de ([80.237.132.66]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VZkjC-0002WY-KH for bitcoin-development@lists.sourceforge.net; Fri, 25 Oct 2013 16:59:18 +0000 Received: from [37.143.74.116] (helo=[192.168.1.5]); authenticated by wp059.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) id 1VZkQk-0005DH-C0; Fri, 25 Oct 2013 18:40:10 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Tamas Blummer <tamas@bitsofproof.com> In-Reply-To: <mailman.289181.1382717617.21953.bitcoin-development@lists.sourceforge.net> Date: Fri, 25 Oct 2013 18:40:08 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <C3388417-98E9-4C80-8E26-05DD9BB6E9C2@bitsofproof.com> References: <mailman.289181.1382717617.21953.bitcoin-development@lists.sourceforge.net> To: bitcoin-development@lists.sourceforge.net X-Mailer: Apple Mail (2.1508) X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1382720354; 4f9a2bd5; X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1VZkjC-0002WY-KH Subject: Re: [Bitcoin-development] Making fee estimation better 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, 25 Oct 2013 16:59:18 -0000 Two thoughts: 1. Please keep it simple, miner will override it either. 2. If block construction algorithm compares alternate chains and not = individual transactions, then receiver can bump up the fee by spending = the unconfirmed output again with higher fee, no need for replacement in = the mempool. Tamas Blummer