Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.80 as permitted sender)
	client-ip=62.13.149.80; envelope-from=pete@petertodd.org;
	helo=outmail149080.authsmtp.com; 
Date: Tue, 3 Dec 2013 07:07:34 -0500
From: Peter Todd <pete@petertodd.org>
To: Taylor Gerring <taylor.gerring@gmail.com>
Message-ID: <20131203120734.GA18895@tilt>
References: <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>
	<CANEZrP1PLKemiUEgMJRGdiZXt7o=0_5fhLKYY0x3Ngb_iEm+2w@mail.gmail.com>
	<CABsx9T322nCvynRCL6Mb9C0f5EuJSfMDTSGiU+_JsYoSCb=_kQ@mail.gmail.com>
	<CANEZrP0P9NTJXs22K8-4hnLkxV7Uo+tjvWKJ8msgxiFgJW6xvg@mail.gmail.com>
	<05CEDEB4-BA29-4ED3-8CFC-D3504727DB4D@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s"
Content-Disposition: inline
In-Reply-To: <05CEDEB4-BA29-4ED3-8CFC-D3504727DB4D@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


--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 03, 2013 at 12:57:23PM +0100, Taylor Gerring wrote:
>=20
> On Dec 3, 2013, at 12:29 PM, Mike Hearn <mike@plan99.net> wrote:
>=20
> > It may be acceptable that receivers don't always receive exactly what t=
hey requested, at least for person-to-business transactions.  For person-to=
-person transactions of course any fee at all is confusing because you intu=
itively expect that if you send 1 mBTC, then 1 mBTC will arrive the other e=
nd. I wonder if we'll end up in a world where buying things from shops invo=
lves paying fees, and (more occasional?) person-to-person transactions tend=
 to be free and people just understand that the money isn't going to be spe=
ndable for a while.
>=20
>=20
> > person-to-business transactions.  For person-to-person transactions
> Why should there be two classes of transactions? Where does paying a loca=
l business at a farmer=E2=80=99s stand lie in that realm? Transactions shou=
ld work the same regardless of who is on the receiving end.
>=20
> > any fee at all is confusing because you intuitively expect that if you =
send 1 mBTC, then 1 mBTC will arrive the other end
> The paradigm of sending money has an explicit cost is not new... I think =
people are used to Western Union/PayPal and associated fees, no?  It=E2=80=
=99s okay to have a fee if it=E2=80=99s reasonable, so let=E2=80=99s inform=
 the user what the estimated cost is to send a transaction in a reasonable =
amount of time.

Indeed.

Transparency on fees is going to be good from a marketing point of view
as well: fact is, Bitcoin transations have fees involved, and if we're
up-front and honest about those fees and what they are and why, we
demystify the system and give people the confidence to tell others about
the cost-advantages of Bitcoin, and at the same time, combat fud about
fees with accurate and honest information.

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

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

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

iQEcBAEBCAAGBQJSncmFAAoJECSBQD2l8JH79HcIAL8lTx+7zKvZXulZKBo+fu/J
b7FzCOgGm/sikmqc+BEdtxG6DC62bvM4x6XHYROgm1hvvfE9EDKLuZRiiphlTFjK
yhGMhk0hlsobaV7m5cztGMIK49GmnVJOTpmfETgMky00npdKOtq5bkSMoiH42y48
dXtU3ZClwlgtlWmwc+4kNL+ePLAHe9y6t23P/1bFSpZ362KS/M0Ul6E3Q+62nddS
lmAcqk9MuxkGJRqvNYFg8zgbyQNZW1HPN+F35ADcFQx3Tpxs9xmo/mSZwA0hOHSq
RehdM3Jq97JeOPpXe3VzEDPAmE79i0McLDTGBKrn3YQ/0pOrYEfBcpEJD/3LduM=
=F1TM
-----END PGP SIGNATURE-----

--SLDf9lqlvOQaIe6s--