Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.175 as permitted sender)
	client-ip=209.85.216.175; envelope-from=etotheipi@gmail.com;
	helo=mail-qc0-f175.google.com; 
Message-ID: <4FA328CF.4020902@gmail.com>
Date: Thu, 03 May 2012 20:54:39 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Wladimir <laanwj@gmail.com>
References: <4FA2095D.9060307@gmail.com>
	<CA+s+GJA2qZxq=V_=Ma0LESOjae49aZHdrpMeJzQS3GtwP5T6=w@mail.gmail.com>
In-Reply-To: <CA+s+GJA2qZxq=V_=Ma0LESOjae49aZHdrpMeJzQS3GtwP5T6=w@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------080306020708080602060002"
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] URI Handling in Bitcoin-Qt
Precedence: list

This is a multi-part message in MIME format.
--------------080306020708080602060002
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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


--------------080306020708080602060002
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On 05/03/2012 01:46 AM, Wladimir wrote:
    <blockquote
cite="mid:CA+s+GJA2qZxq=V_=Ma0LESOjae49aZHdrpMeJzQS3GtwP5T6=w@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div><br>
        </div>
        <div>Label is a label for the destination address, message is a
          freeform message describing the transaction.</div>
        <div><br>
        </div>
        <div>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.</div>
        <div><br>
        </div>
        <div>But I understand that you want to add transaction meta-data
          fields such as contact information, bought items, item prices?</div>
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    I don't want to add fields to the URI-spec, I just want to add them
    <i>to the client</i>.  To me, it is ideal to have separate strings
    for labeling <i>addresses</i> vs labeling <i>transactions</i> --
    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.<br>
    <br>
    For now, it seems that I should count on all important information
    being in the <i>label</i> field, since users creating URLs would
    have to assume anything in the <i>message</i> field will not be
    saved.  Though I imagine the message data will be <i>displayed</i>
    after the URI is clicked, just not saved.<br>
    <br>
    To expand the concept slightly further, it might make sense in the
    future for users to populate the <i>message</i> and <i>label </i>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. <br>
    <br>
    -Alan<br>
    <br>
  </body>
</html>

--------------080306020708080602060002--