Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.78 as permitted sender)
	client-ip=62.13.149.78; envelope-from=pete@petertodd.org;
	helo=outmail149078.authsmtp.net; 
Date: Tue, 3 Dec 2013 06:33:21 -0500
From: Peter Todd <pete@petertodd.org>
To: Drak <drak@zikula.org>
Message-ID: <20131203113321.GB12623@tilt>
References: <5E4597E4-C1C7-4536-8CF0-82EDD7715DAB@plan99.net>
	<l7fpbn$hf6$1@ger.gmane.org>
	<39921E12-B411-4430-9D56-04F53906B109@plan99.net>
	<CAGLkj4C9fyAX1CnB0oZH3BwLRQp6WOo9kLUqDhRUSA6y3LxYvg@mail.gmail.com>
	<CANEZrP1C=Hc-3f-rqQ+wYrPn-eUj52HjN+qRQdJMWvnP+dkK=Q@mail.gmail.com>
	<CAJHLa0P_uzEQ2OG2FTXyD2Zw4RzujNBxKbKD04CSS1sLNpLUUQ@mail.gmail.com>
	<CANEZrP2hf2853w9f4__Ji9v3eRRU0u6pEzPxAmFN+iH067gtnA@mail.gmail.com>
	<CABsx9T3NQDPL6=pz5BD5DsP0qh0x3LJOCj2H3yY5tzL2_DivGA@mail.gmail.com>
	<20131203110354.GA6513@tilt>
	<CANAnSg10KnY=oSM61onYjw5Fp==BwByEeoZUXWfzHqNFjsHYGA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="zx4FCpZtqtKETZ7O"
Content-Disposition: inline
In-Reply-To: <CANAnSg10KnY=oSM61onYjw5Fp==BwByEeoZUXWfzHqNFjsHYGA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Floating fees and SPV clients
Precedence: list


--zx4FCpZtqtKETZ7O
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 03, 2013 at 11:09:51AM +0000, Drak wrote:
> On 3 December 2013 11:03, Peter Todd <pete@petertodd.org> wrote:
>=20
> > UI once both are implemented is to not show anything in the default
> > case, and explain to the user why they have to pay extra in the unusual
> > case where they are spending a whole bunch of dust.
>=20
>=20
> Yes, that's the other problem with a merchant setting a fee - they have no
> idea how large the transaction might be. If you spend a bunch of dust the
> fee could be 2 or 3x the expected fee. Then you might get merchants
> including higher fees by default to account for this. That means we end up
> paying more per kb over time.

Right, which is solved by requiring a fee-per-kb, and only allowing up
to a certain amount to be deducted from the amount paid to pay that
total fee.


But really, we're better off leaving fees visible to the user in the
first place: they're how Bitcoin works and it's not going to change.
(was just talking to Taylor from Hive Wallet about that in person
actually)

--=20
'peter'[:-1]@petertodd.org
000000000000000f9102d27cfd61ea9e8bb324593593ca3ce6ba53153ff251b3

--zx4FCpZtqtKETZ7O
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEbBAEBCAAGBQJSncGBAAoJECSBQD2l8JH767oH92FEzkuF5M3h5J+Wn/uuZaQX
bbUpbptXpqBOC6jx5LgExVSKUUGzuK5Kp7dDjch05SyLjjkJH58v4BLR8HVA5a1o
4EQaXOF+bj8hxp5cmCimEQGxk1ljG7Oj+PZf+sdFRwfzA0uZpChXJC1ipRmGwHz6
saxMpQ+E/idgSVRAqKlXaodYBUPgOoA+0HFGWUIlFuFuHf2z2Qo7B/C9fPHtbKB8
akDVSRNdYSJK3lU0f1UjIhgt+AIBZZ/XZ8iKca06XagISsDqrLLJ3n91lxD81pdR
g0oulqL/4NCKmVC9oz+AubQ/qq3cr6jo2kj8+rseOdJPngSRfIU0kr/X2xJLew==
=/eDS
-----END PGP SIGNATURE-----

--zx4FCpZtqtKETZ7O--