Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id DEC0D92B for ; Thu, 12 Nov 2015 20:13:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 77EB11C7 for ; Thu, 12 Nov 2015 20:13:01 +0000 (UTC) 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 CF48A38A6DE0; Thu, 12 Nov 2015 20:12:30 +0000 (UTC) X-Hashcash: 1:25:151112:bitcoin-dev@lists.linuxfoundation.org::BS99A1p/pkdtSlSo:dCXOm X-Hashcash: 1:25:151112:lf-lists@mattcorallo.com::mnXFc1Or4/5h=v6K:mIga From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Matt Corallo Date: Thu, 12 Nov 2015 20:12:28 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.9-gentoo-r1; KDE/4.14.8; x86_64; ; ) References: <5644ECE6.9090304@mattcorallo.com> In-Reply-To: <5644ECE6.9090304@mattcorallo.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-1" Content-Transfer-Encoding: 7bit Message-Id: <201511122012.29966.luke@dashjr.org> X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 20:13:02 -0000 On Thursday, November 12, 2015 7:47:50 PM Matt Corallo via bitcoin-dev wrote: > With the mempool limiting stuff already in git master, high-priority > relay is disabled when mempools are full. In addition, there was > agreement to take the following steps for 0.12: > > * Mining code will use starting priority for ease of implementation This should be optional, at least for 0.12. > * Default block priority size will be 0 We should not be influencing miner policy by changing defaults. Luke