public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Derber <rderber@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP70 proposed changes
Date: Tue, 18 Feb 2014 15:02:34 -0700	[thread overview]
Message-ID: <CAKwc68wQFtuowgCw3-B5WSAPocdhzv62oS=wM1wfW7Ta-W6Jcg@mail.gmail.com> (raw)
In-Reply-To: <5303B110.70603@bitpay.com>

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 1866 bytes --]

  parent reply	other threads:[~2014-02-18 22:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 17:31 [Bitcoin-development] BIP70 proposed changes Andreas Schildbach
2014-02-18 19:14 ` Ryan X. Charles
2014-02-18 20:15   ` Gavin Andresen
2014-02-18 21:40   ` Andreas Schildbach
2014-02-19 14:10     ` Jeff Garzik
2014-02-19 16:44       ` Mike Hearn
2014-05-06  2:35       ` Odinn Cyberguerrilla
2014-05-06  8:22         ` Alon Muroch
2014-02-18 21:47   ` Peter Todd
2014-02-18 23:41     ` Bernd Jendrissek
2014-02-18 22:02   ` Derber [this message]
2014-02-21 15:34   ` Mike Hearn
2014-03-05 10:18   ` Mike Hearn

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='CAKwc68wQFtuowgCw3-B5WSAPocdhzv62oS=wM1wfW7Ta-W6Jcg@mail.gmail.com' \
    --to=rderber@gmail.com \
    --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