From: Justus Ranvier <justus.ranvier@monetas•net>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Reusable payment codes
Date: Sun, 26 Apr 2015 16:50:00 +0200 [thread overview]
Message-ID: <CAHabJ+McTyW=6Vp1GwTzKefsP9Uo0w+A++sUBwMYJn4L3N__ow@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP20sFUHcabC4+JyR3rv6Xi9AXCUYo__3ZkfWyDjm1YQ7Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
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?
>
[-- Attachment #2: Type: text/html, Size: 1158 bytes --]
next prev parent reply other threads:[~2015-04-26 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 20:00 [Bitcoin-development] " Justus Ranvier
2015-04-24 20:58 ` Gregory Maxwell
[not found] ` <CAHabJ+MtWJS=e3tkGih=xoP4ARgHe8X=D_p9OWTnRJi0z9epBw@mail.gmail.com>
2015-04-25 0:20 ` [Bitcoin-development] Fwd: " Justus Ranvier
[not found] ` <CAHabJ+Oabx80+_1KutfrPUt5QEnMivfNeeh4uJJJOsiHRQqSZw@mail.gmail.com>
2015-04-25 0:21 ` Justus Ranvier
[not found] ` <1AE7B0A2-90EE-42EE-9D30-4DC1B5892E53@newcastle.ac.uk>
[not found] ` <CAHabJ+NDqMN-rQ1BN1TfOjGLQHH-3Wd28LdoF95Agn4HdRrThg@mail.gmail.com>
2015-04-25 0:22 ` Justus Ranvier
[not found] ` <CAAS2fgSAT2otym64oUACpWD8jWLAB6dBusONn-WUx2DK59SB5w@mail.gmail.com>
2015-04-25 2:34 ` Justus Ranvier
2015-04-26 12:58 ` Mike Hearn
2015-04-26 14:50 ` Justus Ranvier [this message]
2015-06-16 16:26 ` [Bitcoin-development] " odinn
2015-06-16 17:46 ` Peter Todd
2015-06-17 5:34 ` odinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHabJ+McTyW=6Vp1GwTzKefsP9Uo0w+A++sUBwMYJn4L3N__ow@mail.gmail.com' \
--to=justus.ranvier@monetas$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox