1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <andy@coinbase.com>) id 1WzWTr-0001Uj-NV
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 19:34:11 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of coinbase.com
designates 209.85.223.173 as permitted sender)
client-ip=209.85.223.173; envelope-from=andy@coinbase.com;
helo=mail-ie0-f173.google.com;
Received: from mail-ie0-f173.google.com ([209.85.223.173])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WzWTp-0006Us-Up
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 19:34:11 +0000
Received: by mail-ie0-f173.google.com with SMTP id y20so715672ier.32
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Jun 2014 12:34:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=chtbMzy4ikctA0qInNHPq4BDgwmQH4KrZl8f35lTNF0=;
b=GQyJQm2EpJD/BvggX3iYWQPiQcbHC+lqbT92VZbgkpxqg0Mm/IHcbVduHs+GOuHuuP
8+lO7W6VENfqSrBuzU+FCvb2NI/tK6DbQpFMvD+suMCwDoz7BazQ2EfjJB4RooEimjlx
UZelAEAr8lTv81QrzpZN6hX636W3qFebG/znCb+6YCP163NgIkXL6hIwUeqxA0m7cwst
qptFqEvRQsvMt82MNyAEvLmnRZp4cxNiXPymcVc+8iSrdU0lgo/uHDZGZu5sw2QbQHYM
j3UOGCEbpZIEgQCT1Vc68UOaREXn7/0gn8gpd/Zp2JgcfHTJAsZQwBvJUgxCqEUoORIk
DgVw==
X-Gm-Message-State: ALoCoQnh+C3OwurTg7tVrtefGZ0FjlKdosMdMUhNtaBQ/IVzJiZeIt0xhp62451FiqJDj6OAhdbR
MIME-Version: 1.0
X-Received: by 10.50.39.45 with SMTP id m13mr36643010igk.1.1403638444038; Tue,
24 Jun 2014 12:34:04 -0700 (PDT)
Received: by 10.42.39.3 with HTTP; Tue, 24 Jun 2014 12:34:03 -0700 (PDT)
In-Reply-To: <BBF86C9B-6B3D-4A03-AC7B-35619C47091F@gmail.com>
References: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
<CAJHLa0Omiz+UhGjSKgYU7+b2YY7aN23w7o8CQntqMePFs7LkjA@mail.gmail.com>
<CANEZrP06gk-JhKaNpvYUTfjFq9AGnCay9=pjUGpVMjMSuX3_ew@mail.gmail.com>
<CAJna-HhX8HOci0KMe4ZScr4QW792S3n5twvU0QhbQe1N_3q7_w@mail.gmail.com>
<6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com>
<CAJHLa0PYfuJg3daPvzPFZpFz7ezH2RHpJ8zyz2g1NDKppM7rWA@mail.gmail.com>
<BBF86C9B-6B3D-4A03-AC7B-35619C47091F@gmail.com>
Date: Tue, 24 Jun 2014 12:34:03 -0700
Message-ID: <CALKy-woTon5bw+hfCKzzqQ1+YBjnn7Yv5ko3J-qfhRZO_VcNmQ@mail.gmail.com>
From: Andy Alness <andy@coinbase.com>
To: Gmail <will.yager@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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: 1WzWTp-0006Us-Up
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
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, 24 Jun 2014 19:34:12 -0000
I somewhat agree with Will (but also with Mike, Jeff, and Charlie.) I
think the idea of letting consumers know advanced details about the
transaction is good and defining these with strong types is also good.
Maybe an arbitrary set of accounting line items would be more
palatable. You could have a line item for state sales tax for example,
or a cash back reward, or a merchant discount like the proposed,
whatever is applicable. It would be a list of amount / label tuples
maybe.
On Tue, Jun 24, 2014 at 12:00 PM, Gmail <will.yager@gmail.com> wrote:
> Ok, wanting structured data is a decent argument, but why this random
> arbitrary case in particular? There are hundreds of fields like this that
> people might want to use.
>
> If we're going to support one random cosmetic field, we might as well
> support them all with a generic structured data format.
>
> I'd rather we just didn't have this essentially pointless "feature" at all.
> Let's try and keep as much cruft as possible out of the payment protocol.
> The textual memo field is already more than sufficient.
>
> On Jun 24, 2014, at 11:48, Jeff Garzik <jgarzik@bitpay.com> wrote:
>
> I think there is nothing wrong with having a numeric memo field, which
> is effectively what this is. Structured rather than unstructured
> data.
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Andy Alness
Software Engineer
Coinbase
San Francisco, CA
|
