From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
Date: Sat, 04 Feb 2012 12:15:02 -0500 [thread overview]
Message-ID: <1328375702.27827.3.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <CAKm8k+0V+LEBESkp18uhQR6CniLogobpxY_34YBqDM0VYcmzzw@mail.gmail.com>
I changed the description of the message parameter to be a bit more
descriptive, however, I dont want to change the name of the parameter
because some clients have already implemented that and I really prefer
to make as minor of changes as possible to this BIP even if it is
officially only a Draft.
Matt
On Sat, 2012-02-04 at 16:03 +0000, Gary Rowe wrote:
> Seems reasonable to me.
>
> On 4 Feb 2012 14:03, <thomasV1@gmx.de> wrote:
> Just another question concerning BIP21:
>
> On the wiki, the description of the "message" parameter reads:
> "message that shown to the user after scanning the QR code"
>
> I believe that the purpose of this parameter is to contain a
> description of the transaction. This has use cases that go
> beyond QR codes.
>
> If I am right, then I would say that naming it "message" is
> misleading. In fact, "message" suggests that a message will be
> sent to someone (the recipient of the funds? a third party?),
> which is not the case here. That parameter should probably be
> called "description".
next prev parent reply other threads:[~2012-02-04 17:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 14:27 [Bitcoin-development] BIP 20 Rejected, process for BIP 21N Amir Taaki
2012-01-31 14:33 ` slush
2012-01-31 14:52 ` Amir Taaki
[not found] ` <CAKm8k+1cHagzj3T27S=h0PueH8EgcCkEajZGgAw7HcQ=N-46ow@mail.gmail.com>
2012-01-31 14:53 ` Gary Rowe
2012-01-31 15:02 ` Gregory Maxwell
2012-01-31 15:04 ` Gary Rowe
2012-01-31 14:59 ` Gregory Maxwell
2012-01-31 16:04 ` Matt Corallo
2012-01-31 18:22 ` Matt Corallo
2012-01-31 19:02 ` Wladimir
2012-01-31 21:42 ` Matt Corallo
2012-01-31 22:14 ` Andreas Schildbach
2012-01-31 22:37 ` Gary Rowe
2012-01-31 22:47 ` Matt Corallo
2012-02-04 14:03 ` thomasV1
2012-02-04 16:03 ` Gary Rowe
2012-02-04 17:15 ` Matt Corallo [this message]
2012-01-31 16:07 ` Luke-Jr
2012-02-02 17:07 Gary Rowe
2012-02-02 17:39 ` Matt Corallo
2012-02-02 17:46 ` Gary Rowe
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=1328375702.27827.3.camel@BMThinkPad.lan.bluematt.me \
--to=bitcoin-list@bluematt.me \
--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