Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.172 as permitted sender)
	client-ip=74.125.82.172; envelope-from=ewillbefull@gmail.com;
	helo=mail-we0-f172.google.com; 
MIME-Version: 1.0
In-Reply-To: <CABsx9T22RQrQAAjGQ+hJix3LDXCdGkfMkxvv7xmxy1n4jM7SOw@mail.gmail.com>
References: <CABsx9T0Ly67ZNJhoRQk0L9Q0-ucq3e=24b5Tg6GRKspRKKtP-g@mail.gmail.com>
	<20130731084538.GL16713@giles.gnomon.org.uk>
	<CABsx9T3Xvnw2H6awgnT7mr-HzJOqCp_nOVM57BD-B9mY4R43aQ@mail.gmail.com>
	<CABsx9T14Dfh8SEe6wsCJjE=S8hTcfDrAUNMBCjtkvM+UH-bAYQ@mail.gmail.com>
	<CAGRKETunznLbBZO1gnS7WZH5sn=TnmKPS4Gz_Nrtocoe5devbw@mail.gmail.com>
	<CABsx9T22RQrQAAjGQ+hJix3LDXCdGkfMkxvv7xmxy1n4jM7SOw@mail.gmail.com>
Date: Wed, 31 Jul 2013 17:52:40 -0600
Message-ID: <CAGRKETuDX9ijUaJuo+U17qBwQZwCb4q4g7sJOQE8V9zJmm=B=Q@mail.gmail.com>
From: E willbefull <ewillbefull@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>,
	bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b5d8815bfba5d04e2d76b5e
Subject: Re: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72
Precedence: list

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

P2SH addresses support exotic transaction outputs, but not all exotic
transactions. This payment protocol can allow for combining multiple
outputs. A PaymentRequest for sending money to multiple parties, for
example, could not fall back to a single address.


On Wed, Jul 31, 2013 at 5:38 PM, Gavin Andresen <gavinandresen@gmail.com>wrote:

> On Thu, Aug 1, 2013 at 9:30 AM, E willbefull <ewillbefull@gmail.com>
> wrote:
> > I think it's important to expect PaymentRequest-only bitcoin URIs in the
> > future. Some types of payments (exotic transactions) may not make sense
> to
> > have a single fallback address.
>
> P2SH addresses already support all exotic transactions.
>
> > Or, a page with a bitcoin URI link may be
> > relying on a separate service provider to assemble the transaction.
>
> Do you mean assemble the PaymentRequest message?  Because the payment
> transaction will always be created by the customer's wallet software.
>
> IF PaymentRequests take over the world and we get 100% wallet software
> support, then I'd be happy to write another BIP that says that a
> bitcoin: URI can be just bitcoin:?request=http...
>
> --
> --
> Gavin Andresen
>

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

<div dir=3D"ltr"><div>P2SH addresses support exotic transaction outputs, bu=
t not all exotic transactions. This payment protocol can allow for combinin=
g multiple outputs. A PaymentRequest for sending money to multiple parties,=
 for example, could not fall back to a single address.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Jul 31, 2013 at 5:38 PM, Gavin Andresen <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Thu, Aug 1, 2013 at 9:3=
0 AM, E willbefull &lt;<a href=3D"mailto:ewillbefull@gmail.com">ewillbefull=
@gmail.com</a>&gt; wrote:<br>

&gt; I think it&#39;s important to expect PaymentRequest-only bitcoin URIs =
in the<br>
&gt; future. Some types of payments (exotic transactions) may not make sens=
e to<br>
&gt; have a single fallback address.<br>
<br>
</div>P2SH addresses already support all exotic transactions.<br>
<div class=3D"im"><br>
&gt; Or, a page with a bitcoin URI link may be<br>
&gt; relying on a separate service provider to assemble the transaction.<br=
>
<br>
</div>Do you mean assemble the PaymentRequest message? =A0Because the payme=
nt<br>
transaction will always be created by the customer&#39;s wallet software.<b=
r>
<br>
IF PaymentRequests take over the world and we get 100% wallet software<br>
support, then I&#39;d be happy to write another BIP that says that a<br>
bitcoin: URI can be just bitcoin:?request=3Dhttp...<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
--<br>
Gavin Andresen<br>
</font></span></blockquote></div><br></div>

--047d7b5d8815bfba5d04e2d76b5e--