From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YmNsl-00061R-1h for bitcoin-development@lists.sourceforge.net; Sun, 26 Apr 2015 14:50:07 +0000 Received: from mail-ig0-f173.google.com ([209.85.213.173]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YmNsj-0000od-UX for bitcoin-development@lists.sourceforge.net; Sun, 26 Apr 2015 14:50:07 +0000 Received: by igblo3 with SMTP id lo3so44774751igb.0 for ; Sun, 26 Apr 2015 07:50:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=rDGudJzMBA2e3Wb9FnOWoLpctWe/ci/LKXi5DD+kiKA=; b=b8gqfOgIeHzJawKjc5VRjlRiE72TIfp4g3RdiOyYA3g3M1nlMshLKhrdcUx03Kidl4 v4TEdEWfBstjI/i5w7fBzWNM7HrErcfZ8M14n+T8puZqSkOEklc+LVc52bhoHp2IXKjY +XpoM6FB5M0l/JFZT51LHkw/bQwsHrvUFN2ecWyAtvdlrDVGeFCrUE8BpLAr7X6aB50W 3L1bgYW1ES5NPDrc7oAJngLtuJ/TjhxYzKHnOoKWmzWwhXsdeiRLlb/mm7mEfWaWjLta fzfU6MennBClR8P2MmC6xb7I5RlIbKsYlYzA/dmki/eMVIYIII51VZdv8hrUGqE8BppW Apvw== X-Gm-Message-State: ALoCoQkNhi/HkPRF51+En8ccGFaeiflor4dv71QANSM7jZAyl97qmF803pxDNglJyu6r4h6O9xGz MIME-Version: 1.0 X-Received: by 10.107.41.72 with SMTP id p69mr8859179iop.58.1430059800673; Sun, 26 Apr 2015 07:50:00 -0700 (PDT) Received: by 10.36.205.135 with HTTP; Sun, 26 Apr 2015 07:50:00 -0700 (PDT) In-Reply-To: References: <1AE7B0A2-90EE-42EE-9D30-4DC1B5892E53@newcastle.ac.uk> Date: Sun, 26 Apr 2015 16:50:00 +0200 Message-ID: From: Justus Ranvier To: Mike Hearn Content-Type: multipart/alternative; boundary=001a1141f3c46d590b0514a1bee8 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1YmNsj-0000od-UX Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Fwd: Reusable payment codes X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Apr 2015 14:50:07 -0000 --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 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
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.

If mercha= nts and customers were using payment codes, they would not need the BIP70 e= quivalents.

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

A payment cod= e behaves much more like an email address than a traditional Bitcoin addres= s.

On Sun, A= pr 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 exten= ding BIP70 and combining it with a simple Subspace style store-and-forward = network?

--001a1141f3c46d590b0514a1bee8--