From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VnUdF-0007Uq-9Q for bitcoin-development@lists.sourceforge.net; Mon, 02 Dec 2013 14:37:53 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.175 as permitted sender) client-ip=209.85.212.175; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f175.google.com; Received: from mail-wi0-f175.google.com ([209.85.212.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VnUdE-0008W7-BH for bitcoin-development@lists.sourceforge.net; Mon, 02 Dec 2013 14:37:53 +0000 Received: by mail-wi0-f175.google.com with SMTP id hi5so4890777wib.14 for ; Mon, 02 Dec 2013 06:37:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Q1cO/i8qits17gZefJdg2rq9hiBvnik1Aj97R4zaj5o=; b=Mes5/qYzgN0ZT3DhyOEs3luU6kHHkHWHfo9zQgSAvZWNS1ks8iGfZamm+WgdqiNaIv a/eA8jAkx250bKm6136NPdF1vsrOZ4P5q5IpjJiElZAnu+peVhYTLCvBhs/9DrLOIt1x 6HvK9dOzOiCJPuyj7vVRM4NsAf1bFnhDyTdk3unV0zMMne+wBy6oWl7xNpX2IA+d1IhV 1rR7qMqx1vWHIh4pDCNVi6gZvXkCT4D3USmg45rcdlDFF1v4pYvPTM5RA9CwQlYeykT8 dVVJktgtXhkTeb9FW3eqvx+g7p+3YzlTPMN76aYloEETRVZEkfXoUSbGRgsJMV2t3vkq NMKg== X-Gm-Message-State: ALoCoQljbhPPf5Gh0hcs0P/bdLZhvQp3MW4OO1MCuwc/JMDiacOq1tU52PruDU3MEnTEzYKYKdi9 MIME-Version: 1.0 X-Received: by 10.194.240.41 with SMTP id vx9mr2276072wjc.70.1385995065989; Mon, 02 Dec 2013 06:37:45 -0800 (PST) Received: by 10.194.164.164 with HTTP; Mon, 2 Dec 2013 06:37:45 -0800 (PST) In-Reply-To: References: <5E4597E4-C1C7-4536-8CF0-82EDD7715DAB@plan99.net> <39921E12-B411-4430-9D56-04F53906B109@plan99.net> Date: Mon, 2 Dec 2013 09:37:45 -0500 Message-ID: From: Jeff Garzik To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) 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 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitpay.com] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1VnUdE-0008W7-BH Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Floating fees and SPV clients 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: Mon, 02 Dec 2013 14:37:53 -0000 On Mon, Dec 2, 2013 at 9:33 AM, Mike Hearn wrote: > "The payment protocol at least would need some notion of fee, or possibly > (better?) the ability for a recipient to specify some inputs as well as some > outputs." BitPay noticed this detail last week. We were noticing that some transactions were not even reaching our bitcoind border routers (edge nodes), due to low/no fees. That led to a long discussion of all things fee-related. SPV fees are a big issue. Getting child-pays-for-parent in some form out to miners is another. Getting a smart, dynamic fee market Gavin mentions is a big need. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/