Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <rderber@gmail.com>) id 1WFskT-0002I5-3x
	for bitcoin-development@lists.sourceforge.net;
	Tue, 18 Feb 2014 22:02:41 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.170 as permitted sender)
	client-ip=209.85.220.170; envelope-from=rderber@gmail.com;
	helo=mail-vc0-f170.google.com; 
Received: from mail-vc0-f170.google.com ([209.85.220.170])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WFskS-0005A4-Cx
	for bitcoin-development@lists.sourceforge.net;
	Tue, 18 Feb 2014 22:02:41 +0000
Received: by mail-vc0-f170.google.com with SMTP id hu8so14087201vcb.1
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 18 Feb 2014 14:02:35 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.220.225.71 with SMTP id ir7mr2176561vcb.50.1392760954917;
	Tue, 18 Feb 2014 14:02:34 -0800 (PST)
Received: by 10.58.137.72 with HTTP; Tue, 18 Feb 2014 14:02:34 -0800 (PST)
In-Reply-To: <5303B110.70603@bitpay.com>
References: <le05ca$qn5$1@ger.gmane.org>
	<5303B110.70603@bitpay.com>
Date: Tue, 18 Feb 2014 15:02:34 -0700
Message-ID: <CAKwc68wQFtuowgCw3-B5WSAPocdhzv62oS=wM1wfW7Ta-W6Jcg@mail.gmail.com>
From: Derber <rderber@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=089e0115fa16f997ec04f2b56d70
X-Spam-Score: 0.6 (/)
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
	(rderber[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.2 MISSING_HEADERS        Missing To: header
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	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: 1WFskS-0005A4-Cx
Subject: Re: [Bitcoin-development] BIP70 proposed changes
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: Tue, 18 Feb 2014 22:02:41 -0000

--089e0115fa16f997ec04f2b56d70
Content-Type: text/plain; charset=ISO-8859-1

Any possibility of a UNIX UTC timestamp field in the customer payment
message?

For many transactions, the exact time of payment is when it is 'made' by
the customer and not when 'requested' by the retailer or later mined. The
blockchain time is an aggregate for the block and can differ significantly
from transaction time so its value is limited.

Small slices of time can greatly impact the transaction value.  If we are
ultimately taxed as a currency, an exact time will for the transaction will
impact US GAAP accounting and the transaction's tax accounting. A time
field may also support 'first come first served' retailer programs and time
sensitive promotions.

--089e0115fa16f997ec04f2b56d70
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:19.3=
3333396911621px">Any possibility of a UNIX UTC timestamp field in the custo=
mer payment=A0</span><span style=3D"font-family:arial,sans-serif;font-size:=
19.33333396911621px">message?</span><div>
<span style=3D"font-family:arial,sans-serif;font-size:19.33333396911621px">=
<br></span></div><div><span style=3D"font-family:arial,sans-serif;font-size=
:19.33333396911621px">For many transactions, the exact time of payment is w=
hen it is &#39;made&#39; by the customer and not when &#39;requested&#39; b=
y the retailer or later mined. The blockchain time is an aggregate for the =
block and can differ significantly from transaction time so its value is li=
mited.</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:19.3333339691162=
1px"><br></span></div><div><span style=3D"font-family:arial,sans-serif;font=
-size:19.33333396911621px">Small slices of time can </span><span style=3D"f=
ont-family:arial,sans-serif;font-size:19.33333396911621px">greatly impact t=
he transaction value. =A0If we are ultimately taxed as a currency, an exact=
 time will for the transaction will impact US GAAP accounting and the trans=
action&#39;s tax accounting. A time field may=A0</span><span style=3D"font-=
family:arial,sans-serif;font-size:19.33333396911621px">also support &#39;fi=
rst=A0</span><font face=3D"arial, sans-serif"><span style=3D"font-size:19.3=
3333396911621px">come first served&#39;=A0</span></font><span style=3D"font=
-family:arial,sans-serif;font-size:19.33333396911621px">retailer programs</=
span><span style=3D"font-family:arial,sans-serif;font-size:19.3333339691162=
1px">=A0</span><font face=3D"arial, sans-serif"><span style=3D"font-size:19=
.33333396911621px">and time sensitive=A0promotions</span></font><span style=
=3D"font-family:arial,sans-serif;font-size:19.33333396911621px">.</span></d=
iv>
<div class=3D"gmail_extra"><br></div></div>

--089e0115fa16f997ec04f2b56d70--