From: Wladimir <laanwj@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP72 amendment proposal
Date: Fri, 12 Sep 2014 11:55:01 +0200 [thread overview]
Message-ID: <CA+s+GJAjPdLB3jn-U6NbN0LvBKz+C5fDdbdEhFPKXUiTjyZDEA@mail.gmail.com> (raw)
In-Reply-To: <luuee6$as3$1@ger.gmane.org>
On Fri, Sep 12, 2014 at 11:29 AM, Andreas Schildbach
<andreas@schildbach.de> wrote:
> This is the discussion post corresponding to this PR:
> https://github.com/bitcoin/bips/pull/106
>
> "Amend BIP72 by an "h" parameter, which contains a hash of the
> PaymentRequest message that is fetched via the "r" parameter.
>
> The hash is meant to link the trust anchor (e.g. the QR code) to the
> payment request message in a secure way. This will solve the problem
> several apps are comparing address+amount fields as a workaround
> instead, preventing some advanced BIP70 usecases. When these apps read a
> matching hash, they need not compare any of the other fields.
Sounds like a good idea to me.
I had no idea that some clients were comparing addresses and amounts
in the URI with the payment request for security, that seems like a
hacky and inflexible way. This is much better.
Wladimir
next prev parent reply other threads:[~2014-09-12 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 9:29 [Bitcoin-development] BIP72 amendment proposal Andreas Schildbach
2014-09-12 9:55 ` Wladimir [this message]
[not found] <mailman.341412.1410515709.2178.bitcoin-development@lists.sourceforge.net>
2014-09-12 10:11 ` Mark van Cuijk
2014-09-12 11:07 ` Andreas Schildbach
2014-09-12 13:49 ` Mike Hearn
2014-09-12 14:15 ` Jeff Garzik
2014-09-12 14:36 ` Andreas Schildbach
2014-09-12 15:25 ` Christophe Biocca
2014-09-12 15:33 ` Christophe Biocca
2014-09-12 15:37 ` Mike Hearn
2014-09-12 16:31 ` Mike Hearn
2014-09-12 18:43 ` Aaron Voisine
2014-09-15 7:43 ` Andreas Schildbach
2014-09-15 7:12 ` Andreas Schildbach
2014-09-12 15:36 ` Mike Hearn
[not found] <mailman.342174.1410547421.2163.bitcoin-development@lists.sourceforge.net>
2014-09-12 20:59 ` Mark van Cuijk
2014-09-13 8:53 ` Wladimir
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=CA+s+GJAjPdLB3jn-U6NbN0LvBKz+C5fDdbdEhFPKXUiTjyZDEA@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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