Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.175 as permitted sender)
	client-ip=209.85.214.175; envelope-from=etotheipi@gmail.com;
	helo=mail-ob0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <CABsx9T2UBQXzDPj0zHio+9i0uKNqiPYwL=kYgWKSirXRvckQ4g@mail.gmail.com>
References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com>
	<20121128233619.GA6368@giles.gnomon.org.uk>
	<CABsx9T09FYf2RTaMpmujt3qwTFc2JgnREH_7Hyk2mnCgb3CvAw@mail.gmail.com>
	<20121129170713.GD6368@giles.gnomon.org.uk>
	<CANEZrP233CytLs3PWBQ1TyuBTMv4sLGJkEMeGWYq5xRi+iLKew@mail.gmail.com>
	<20121129185330.GE6368@giles.gnomon.org.uk>
	<CABsx9T35qD_xJEVw002eAhJ1kr6x5aMU7RpD+U84XEOZXmXcYw@mail.gmail.com>
	<CANEZrP2riPBViBqAOWfY9uSQwoEm=gN108JU988XvouMbai1Ug@mail.gmail.com>
	<CABsx9T023aw11cq6iiZhT3cgfNYJXr=qG40Fzc7rYZOimJ=62w@mail.gmail.com>
	<50C03BDA.6010600@petersson.at>
	<CANEZrP1iS4_MFi2=3Qa4_rSGXe5EK8B0wWy43hXJOeKp-SfpPg@mail.gmail.com>
	<CABsx9T2UBQXzDPj0zHio+9i0uKNqiPYwL=kYgWKSirXRvckQ4g@mail.gmail.com>
Date: Thu, 6 Dec 2012 13:13:00 -0500
Message-ID: <CALf2ePx5jS__L_2bTtU7duAbDfeinEapzARuGEJ-XCbkK=TxNA@mail.gmail.com>
From: Alan Reiner <etotheipi@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0444e8a59dffc004d0330ce4
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment Protocol Proposal:
	Invoices/Payments/Receipts
Precedence: list

--f46d0444e8a59dffc004d0330ce4
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Dec 6, 2012 at 11:56 AM, Gavin Andresen <gavinandresen@gmail.com>wrote:

> When I say "pass around" I'm not thinking of users copying and pasting,
> that would be a terrible user experience; all of that communication needs
> to happen automatically behind the scenes. Lets tackle that after we've got
> the simpler customer-pays-merchant flow working nicely
> (funded-escrow-pays-merchant is a subset of that, anyway).


I think that the "pass around" method needs to happen in addition to the
methods of transparent protocols that occur behind the scenes.  For one,
there's a lot of CONOPs that need to be worked out by getting knowledgeable
people using it, and providing feedback about how it could/should/will be
used and how it could be improved.  The pass-around method is simpler to
implement and still usable by the types of users that will be using it in
the beginning -- experts.  Also, I see that for very large, important
multi-sig tx/contracts/escrow, the "manual" method might be preferred --
much the same way many people prefer manual-transmission cars even though
automatics are "easier" -- some people/organizations will want the control.


I'm all for protocols that enable higher-level access to this
functionality, I'm just saying there should be lower-level access, too.

--f46d0444e8a59dffc004d0330ce4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Dec 6, 20=
12 at 11:56 AM, Gavin Andresen <span dir=3D"ltr">&lt;<a href=3D"mailto:gavi=
nandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">When I say &quot;pass around&quot; I&#39;m n=
ot thinking of users copying and pasting, that would be a terrible user exp=
erience; all of that communication needs to happen automatically behind the=
 scenes. Lets tackle that after we&#39;ve got the simpler customer-pays-mer=
chant flow working nicely (funded-escrow-pays-merchant is a subset of that,=
 anyway).</blockquote>
</div><br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_ex=
tra">I think that the &quot;pass around&quot; method needs to happen in add=
ition to the methods of transparent protocols that occur behind the scenes.=
 =A0For one, there&#39;s a lot of CONOPs that need to be worked out by gett=
ing knowledgeable people using it, and providing feedback about how it coul=
d/should/will be used and how it could be improved. =A0The pass-around meth=
od is simpler to implement and still usable by the types of users that will=
 be using it in the beginning -- experts. =A0Also, I see that for very larg=
e, important multi-sig tx/contracts/escrow, the &quot;manual&quot; method m=
ight be preferred -- much the same way many people prefer manual-transmissi=
on cars even though automatics are &quot;easier&quot; -- some people/organi=
zations will want the control. =A0=A0</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I&#39;m all=
 for protocols that enable higher-level access to this functionality, I&#39=
;m just saying there should be lower-level access, too.</div><div class=3D"=
gmail_extra">
<br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><=
br></div><div class=3D"gmail_extra"><br></div>

--f46d0444e8a59dffc004d0330ce4--