public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Tamas Blummer <tamas@bitsofproof.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP 70 refund field
Date: Fri, 28 Mar 2014 14:00:27 +0100	[thread overview]
Message-ID: <CANEZrP3xcRrPsR+nCDAWgTaXg=ADGH1KjrwgLew7V2eC9ghexg@mail.gmail.com> (raw)
In-Reply-To: <47379042-C1B6-4E22-8FF7-4EE9FDC095AC@bitsofproof.com>

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

>
> What is too abstract in a contact list ? If the payment comes with a tag
> like refund the UI could display as such and if it comes with e.g. VAT then
> that.
>

How is this any different? The tag in this case is the address and the
payment is being delivered by the block chain (direct submission for
user->merchant is easier than merchant->user) so we can't stuff extra data
anywhere else. Then the UI knows it was a refund payment and not for
anything else.

I don't see the relevance of VAT here.

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

  reply	other threads:[~2014-03-28 13:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 11:07 [Bitcoin-development] BIP 70 refund field Mike Hearn
2014-03-28 11:25 ` Andreas Schildbach
2014-03-28 11:31   ` Mike Hearn
2014-03-28 16:59     ` Andreas Schildbach
2014-03-28 18:19       ` Mike Hearn
2014-03-28 20:56         ` Andreas Schildbach
2014-03-29  9:27           ` Roy Badami
2014-03-29 13:29             ` Mike Hearn
2014-03-30 17:21               ` Andreas Schildbach
2014-03-28 11:38   ` Wladimir
2014-03-28 11:45     ` Tamas Blummer
2014-03-28 11:46       ` Mike Hearn
2014-03-28 11:54         ` Tamas Blummer
2014-03-28 12:27           ` Mike Hearn
2014-03-28 12:55             ` Tamas Blummer
2014-03-28 13:00               ` Mike Hearn [this message]
2014-03-28 13:09                 ` Tamas Blummer
2014-03-28 11:30 ` Tamas Blummer
2014-03-28 13:18   ` Tamas Blummer
2014-03-28 14:01     ` Gavin Andresen
2014-03-28 14:06       ` Mike Hearn
2014-03-28 14:27       ` Tamas Blummer
2014-03-28 15:23         ` Mike Hearn
2014-03-28 15:26           ` Tamas Blummer
2014-03-28 16:34             ` Mike Hearn
2014-03-28 16:45               ` Tamas Blummer
2014-03-31  9:23 ` Peter Todd

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='CANEZrP3xcRrPsR+nCDAWgTaXg=ADGH1KjrwgLew7V2eC9ghexg@mail.gmail.com' \
    --to=mike@plan99.net \
    --cc=andreas@schildbach.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=tamas@bitsofproof.com \
    /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