MIME-Version: 1.0
In-Reply-To: <CANEZrP20sFUHcabC4+JyR3rv6Xi9AXCUYo__3ZkfWyDjm1YQ7Q@mail.gmail.com>
References: <CAHabJ+Mn0=vfLvTJ+z3tx8cFAAuLD1pLp4rOe3pM6MtCrCxjwg@mail.gmail.com>
	<1AE7B0A2-90EE-42EE-9D30-4DC1B5892E53@newcastle.ac.uk>
	<CAHabJ+NDqMN-rQ1BN1TfOjGLQHH-3Wd28LdoF95Agn4HdRrThg@mail.gmail.com>
	<CAHabJ+PMdQ-f7G8RNz0R7mfGUwBMAsnCyO=NmQhxyq0+gB1aPg@mail.gmail.com>
	<CAAS2fgSAT2otym64oUACpWD8jWLAB6dBusONn-WUx2DK59SB5w@mail.gmail.com>
	<CAHabJ+O7n=_ACXJx6_2DzoFC6h=2dk0aR3u3_LZhHgDut1gNMA@mail.gmail.com>
	<CANEZrP20sFUHcabC4+JyR3rv6Xi9AXCUYo__3ZkfWyDjm1YQ7Q@mail.gmail.com>
Date: Sun, 26 Apr 2015 16:50:00 +0200
Message-ID: <CAHabJ+McTyW=6Vp1GwTzKefsP9Uo0w+A++sUBwMYJn4L3N__ow@mail.gmail.com>
From: Justus Ranvier <justus.ranvier@monetas.net>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=001a1141f3c46d590b0514a1bee8
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Reusable payment codes
Precedence: list

--001a1141f3c46d590b0514a1bee8
Content-Type: text/plain; charset=UTF-8

Payment codes establish the identity of the payer and allow for simpler
methods for identifying the payee, and automatically provide the payee with
the information they need to send a refund.

If merchants and customers were using payment codes, they would not need
the BIP70 equivalents.

I think the best way to explain payment codes is that they add the missing
"from address" to transactions which users want, but we've had to tell them
they can't have.

A payment code behaves much more like an email address than a traditional
Bitcoin address.

On Sun, Apr 26, 2015 at 2:58 PM, Mike Hearn <mike@plan99.net> wrote:

> Could you maybe write a short bit of text comparing this approach to
> extending BIP70 and combining it with a simple Subspace style
> store-and-forward network?
>

--001a1141f3c46d590b0514a1bee8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Payment codes establish the identity of the payer and allo=
w for simpler methods for identifying the payee, and automatically provide =
the payee with the information they need to send a refund.<br><br>If mercha=
nts and customers were using payment codes, they would not need the BIP70 e=
quivalents.<br><br>I think the best way to explain payment codes is that th=
ey add the missing &quot;from address&quot; to transactions which users wan=
t, but we&#39;ve had to tell them they can&#39;t have.<br><br>A payment cod=
e behaves much more like an email address than a traditional Bitcoin addres=
s.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, A=
pr 26, 2015 at 2:58 PM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"mailto:=
mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"=
>Could you maybe write a short bit of text comparing this approach to exten=
ding BIP70 and combining it with a simple Subspace style store-and-forward =
network?</div></div>
</blockquote></div><br></div>

--001a1141f3c46d590b0514a1bee8--