From: Alan Reiner <etotheipi@gmail•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] URI Handling in Bitcoin-Qt
Date: Thu, 03 May 2012 20:54:39 -0400 [thread overview]
Message-ID: <4FA328CF.4020902@gmail.com> (raw)
In-Reply-To: <CA+s+GJA2qZxq=V_=Ma0LESOjae49aZHdrpMeJzQS3GtwP5T6=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
On 05/03/2012 01:46 AM, Wladimir wrote:
>
> Label is a label for the destination address, message is a freeform
> message describing the transaction.
>
> I don't think the message is currently stored in the Satoshi client.
> That feature is somewhere on our way-too-long issue and todo list.
>
> But I understand that you want to add transaction meta-data fields
> such as contact information, bought items, item prices?
>
>
I don't want to add fields to the URI-spec, I just want to add them /to
the client/. To me, it is ideal to have separate strings for labeling
/addresses/ vs labeling /transactions/ -- i.e. different strings would
show up in the address book (owner info) than what shows up in the
transaction history (purchase info). I say it's ideal because that
concept seems to fit perfectly with availability of "label=" and
"message=" fields in BIP 21, but it won't actually work if Bitcoin-Qt
won't/can't do it that way.
For now, it seems that I should count on all important information being
in the /label/ field, since users creating URLs would have to assume
anything in the /message/ field will not be saved. Though I imagine the
message data will be /displayed/ after the URI is clicked, just not saved.
To expand the concept slightly further, it might make sense in the
future for users to populate the /message/ and /label /fields with lots
of data, using newlines. The first line would be used as a summary and
displayed in the address book and ledger. The extra lines would all be
displayed when the user opens up a details window. All of it would be
automatically generated by the merchant, and the purchaser would end up
with detailed documentation on every purchase they've made for zero effort.
-Alan
[-- Attachment #2: Type: text/html, Size: 2515 bytes --]
next prev parent reply other threads:[~2012-05-04 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 4:28 Alan Reiner
2012-05-03 5:46 ` Wladimir
2012-05-04 0:54 ` Alan Reiner [this message]
2012-05-03 7:16 ` Andreas Schildbach
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=4FA328CF.4020902@gmail.com \
--to=etotheipi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/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