Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z2zZs-00059c-0t for bitcoin-development@lists.sourceforge.net; Thu, 11 Jun 2015 10:19:16 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.180 as permitted sender) client-ip=209.85.212.180; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f180.google.com; Received: from mail-wi0-f180.google.com ([209.85.212.180]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z2zZr-0002a6-3s for bitcoin-development@lists.sourceforge.net; Thu, 11 Jun 2015 10:19:16 +0000 Received: by wiwd19 with SMTP id d19so70809102wiw.0 for ; Thu, 11 Jun 2015 03:19:09 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.206.229 with SMTP id lr5mr28743806wic.86.1434017949112; Thu, 11 Jun 2015 03:19:09 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.194.16.40 with HTTP; Thu, 11 Jun 2015 03:19:09 -0700 (PDT) In-Reply-To: References: Date: Thu, 11 Jun 2015 12:19:09 +0200 X-Google-Sender-Auth: Z4ZZRfgWaZaSWN5VKGUxnShkjmo Message-ID: From: Mike Hearn To: Aaron Voisine Content-Type: multipart/alternative; boundary=001a11c38a227560cd05183b524f 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: 1Z2zZr-0002a6-3s 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 10:19:16 -0000 --001a11c38a227560cd05183b524f Content-Type: text/plain; charset=UTF-8 > > If we assume that transactions are being dropped in an unpredictable way > when blocks are full, knowing the network congestion *right now* is > critical, and even then you just have to hope that someone who wants that > space more than you do doesn't show up after you disconnect. > Yeah, my proposal is not intended to function correctly with full blocks, as Bitcoin cannot work at all in such a state. It assumes that fees only change slowly and that transactions are being cleared normally. --001a11c38a227560cd05183b524f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
If we assume that transactions = are being dropped in an unpredictable way when blocks are full, knowing the= network congestion *right now* is critical, and even then you just have to= hope that someone who wants that space more than you do doesn't show u= p after you disconnect.

Yeah, my prop= osal is not intended to function correctly with full blocks, as Bitcoin can= not work at all in such a state. It assumes that fees only change slowly an= d that transactions are being cleared normally.
--001a11c38a227560cd05183b524f--