From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VnnLx-0002C0-GF for bitcoin-development@lists.sourceforge.net; Tue, 03 Dec 2013 10:37:17 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org designates 74.125.82.172 as permitted sender) client-ip=74.125.82.172; envelope-from=drak@zikula.org; helo=mail-we0-f172.google.com; Received: from mail-we0-f172.google.com ([74.125.82.172]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VnnLw-00030V-MR for bitcoin-development@lists.sourceforge.net; Tue, 03 Dec 2013 10:37:17 +0000 Received: by mail-we0-f172.google.com with SMTP id w62so7692721wes.31 for ; Tue, 03 Dec 2013 02:37:10 -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:from:date :message-id:subject:to:cc:content-type; bh=uH6Ylw7ZuEiBQl8MhNnspEC4Stg/+yrdLSmEnHXPDAk=; b=ZQOCk34SwEYKrBZsBB16TJqMDE5raEidFXVtYsiJxL3KmmPQfUXizjqB0hpPfu+AwZ 1R0tpkL5olFd817Fr/fsiCq/c4U6HcAplGXV1sGn8l7ZDL3nP/LTuLA6ChYrV6I71gJL LyrcVWCd52wSH6ZwEc8uRzEirD3TFjgGjECgEs6MkNOZ+w4Zpqe81ghWCjkdiLhvKe+9 wOf4fmpl++pBVQaWih5t9gj7A0d0fOBfVX2JAUg9M/ovnGmTG+QQacPnE5oSijIl4hJ1 B6GPxLyTnrP6v8Kf0uAxysGhaGPDEpQz1c7J+q146eVJ0X8ThPZtu9by+SrH6F79/897 puGg== X-Gm-Message-State: ALoCoQkQlnY2qBv1bmEHbrpcmkpopnfyXjiCHHrIBOFdr6bjuaY/eLNXhAa05sgT5aXrkxfv7Pp5 X-Received: by 10.180.103.193 with SMTP id fy1mr1861742wib.10.1386067030414; Tue, 03 Dec 2013 02:37:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.93.105 with HTTP; Tue, 3 Dec 2013 02:36:50 -0800 (PST) In-Reply-To: References: <5E4597E4-C1C7-4536-8CF0-82EDD7715DAB@plan99.net> <39921E12-B411-4430-9D56-04F53906B109@plan99.net> From: Drak Date: Tue, 3 Dec 2013 10:36:50 +0000 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=f46d04428e3afbb21704ec9ee05f 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 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1VnnLw-00030V-MR 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: Tue, 03 Dec 2013 10:37:17 -0000 --f46d04428e3afbb21704ec9ee05f Content-Type: text/plain; charset=UTF-8 I dont like the idea of putting the min fee in the hands of the receiver. Seems like that will work against the best interests of senders in the long run. Why not try a different path of calculating the min fee like difficulty retarget. You can analyse the last 2016 blocks to find the average fee accepted per kb (which would include transactions that were included without fees) and then write that into the block as a soft recommendation that wallets could use in the UI. This way the price can vary up and down according to what people were willing to spend on fees and miners willing to accept. I absolutely do not trust vendors to set fees. I think it has to be based on what senders are willing to pay and what miners are willing to accept. Drak --f46d04428e3afbb21704ec9ee05f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I dont like the idea of putting= the min fee in the hands of the receiver. Seems like that will work agains= t the best interests of senders in the long run.=C2=A0

Why not try a different path of calcul= ating the min fee like difficulty retarget. You can analyse the last 2016 b= locks to find the average fee accepted per kb (which would include transact= ions that were included without fees) and then write that into the block as= a soft recommendation that wallets could use in the UI. This way the price= can vary up and down according to what people were willing to spend on fee= s and miners willing to accept. =C2=A0

I absolutel= y do not trust vendors to set fees. I think it has to be based on what send= ers are willing to pay and what miners are willing to accept.

Drak<= /div>

--f46d04428e3afbb21704ec9ee05f--