From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z36eX-0007t9-IG for bitcoin-development@lists.sourceforge.net; Thu, 11 Jun 2015 17:52:33 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.43 as permitted sender) client-ip=74.125.82.43; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f43.google.com; Received: from mail-wg0-f43.google.com ([74.125.82.43]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z36eW-0002bH-Ib for bitcoin-development@lists.sourceforge.net; Thu, 11 Jun 2015 17:52:33 +0000 Received: by wgme6 with SMTP id e6so9389441wgm.2 for ; Thu, 11 Jun 2015 10:52:26 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.157.168 with SMTP id wn8mr18205623wjb.79.1434045146572; Thu, 11 Jun 2015 10:52:26 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.194.16.40 with HTTP; Thu, 11 Jun 2015 10:52:26 -0700 (PDT) In-Reply-To: <5579C0FE.8080701@thinlink.com> References: <20150611131048.GA24053@savin.petertodd.org> <5579C0FE.8080701@thinlink.com> Date: Thu, 11 Jun 2015 19:52:26 +0200 X-Google-Sender-Auth: PIpP325soyR2ToU4BLYexWeY2M4 Message-ID: From: Mike Hearn To: Tom Harding Content-Type: multipart/alternative; boundary=089e0122e9688dac21051841a701 X-Spam-Score: -0.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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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 X-Headers-End: 1Z36eW-0002bH-Ib Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2015 17:52:33 -0000 --089e0122e9688dac21051841a701 Content-Type: text/plain; charset=UTF-8 > > > Re: "dropped in an unpredictable way" - transactions would be dropped > > lowest fee/KB first, a completely predictable way. > > Quite agreed. No, Aaron is correct. It's unpredictable from the perspective of the user sending the transaction, and as they are the ones picking the fees, that is what matters. --089e0122e9688dac21051841a701 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> Re: "dropped in an un= predictable way" - transactions would be dropped
> lowest fee/KB first, a completely predictable way.

Quite agreed.=C2=A0

No, Aaron is co= rrect. It's unpredictable from the perspective of the user sending the = transaction, and as they are the ones picking the fees, that is what matter= s.
--089e0122e9688dac21051841a701--