+Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]

+ helo=mx.sourceforge.net)

+ by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)

+ (envelope-from <watsonbladd@gmail.com>) id 1Tds1k-0000k1-9m

+ for bitcoin-development@lists.sourceforge.net;

+ Thu, 29 Nov 2012 00:30:52 +0000

+Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com

+ designates 209.85.212.181 as permitted sender)

+ client-ip=209.85.212.181; envelope-from=watsonbladd@gmail.com;

+ helo=mail-wi0-f181.google.com;

+Received: from mail-wi0-f181.google.com ([209.85.212.181])

+ by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)

+ (Exim 4.76) id 1Tds1j-0006sB-Ib

+ for bitcoin-development@lists.sourceforge.net;

+ Thu, 29 Nov 2012 00:30:52 +0000

+Received: by mail-wi0-f181.google.com with SMTP id hm2so4587328wib.10

+ for <bitcoin-development@lists.sourceforge.net>;

+ Wed, 28 Nov 2012 16:30:45 -0800 (PST)

+MIME-Version: 1.0

+Received: by 10.180.84.101 with SMTP id x5mr35686251wiy.18.1354149045426; Wed,

+ 28 Nov 2012 16:30:45 -0800 (PST)

+Sender: watsonbladd@gmail.com

+Received: by 10.194.16.9 with HTTP; Wed, 28 Nov 2012 16:30:45 -0800 (PST)

+In-Reply-To: <20121128233619.GA6368@giles.gnomon.org.uk>

+References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com>

+ <20121128233619.GA6368@giles.gnomon.org.uk>

+Date: Wed, 28 Nov 2012 18:30:45 -0600

+X-Google-Sender-Auth: ItoHS4Pkx4v2LiyVx7HhzDE3k4M

+Message-ID: <CACsn0cmsoS5riXAV7eWMfTFzSNwbjWEUNCa39m1MgKGxvRKCmg@mail.gmail.com>

+From: Watson Ladd <wbl@uchicago.edu>

+To: Roy Badami <roy@gnomon.org.uk>

+Content-Type: multipart/alternative; boundary=f46d0444048ed35afc04cf9764bd

+X-Spam-Score: -0.5 (/)

+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.

+ See http://spamassassin.org/tag/ for more details.

+ -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for

+ sender-domain

+ 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider

+ (watsonbladd[at]gmail.com)

+ -0.0 SPF_PASS SPF: sender matches SPF record

+ 1.0 HTML_MESSAGE BODY: HTML included in message

+ 0.1 DKIM_SIGNED Message has a DKIM or DK signature,

+ not necessarily valid

+ -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature

+X-Headers-End: 1Tds1j-0006sB-Ib

+Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>

+Subject: Re: [Bitcoin-development] Payment Protocol Proposal:

+ Invoices/Payments/Receipts

+X-BeenThere: bitcoin-development@lists.sourceforge.net

+X-Mailman-Version: 2.1.9

+Precedence: list

+List-Id: <bitcoin-development.lists.sourceforge.net>

+List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,

+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>

+List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>

+List-Post: <mailto:bitcoin-development@lists.sourceforge.net>

+List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>

+List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,

+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>

+X-List-Received-Date: Thu, 29 Nov 2012 00:30:52 -0000

+

+--f46d0444048ed35afc04cf9764bd

+Content-Type: text/plain; charset=UTF-8

+

+After doing more thinking, what about letting a spend sign more information

+associated with the transaction, such as a transaction ID provided by the

+merchant? This seems to solve a lot of the problems being put forward, with

+much less complexity.

+

+--f46d0444048ed35afc04cf9764bd

+Content-Type: text/html; charset=UTF-8

+

+After doing more thinking, what about letting a spend sign more information associated with the transaction, such as a transaction ID provided by the merchant? This seems to solve a lot of the problems being put forward, with much less complexity.

+

+--f46d0444048ed35afc04cf9764bd--

+

+