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
|
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 <jgarzik@bitpay.com>) id 1WzRc0-0008EN-8E
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 14:22:16 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.179 as permitted sender)
client-ip=74.125.82.179; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f179.google.com;
Received: from mail-we0-f179.google.com ([74.125.82.179])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WzRby-0002pu-8T
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Jun 2014 14:22:16 +0000
Received: by mail-we0-f179.google.com with SMTP id w62so425066wes.24
for <bitcoin-development@lists.sourceforge.net>;
Tue, 24 Jun 2014 07:22:07 -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:from:date
:message-id:subject:to:cc:content-type;
bh=truP/UTg3Vwxqs3p+/91qJMIjo+gFEq3489+UuvkxZw=;
b=GmKSNA/0pDx4+cGO3WuMaZBgxLo0Waabuz916YpENdUtfEdAnsDzMRjhhW/pfsHsTg
jvHXB4e3OCM1GoXDB7OiCDDFCjBSLED+P8FWO9+0NaZ9qoD3ceDr/Orvhv6GMhe4t7PZ
VsND14BxByp5/ax37HZDNkUogqb89RAUTy4p4zMJ9bjKUjvffMabPVb/IrlbVYw+wwlh
NxDiptm6qK0/of9Jr+UsH8oZVVpmvuyCpgIiuTvOP3V8K96gDlVu01PyVMdUrCIYj4zf
glPawW8lRgo/BsAm/TAtnvQHSl0cdzJCu6IZhImvtBF2wk8a3gnTIkoYS1/YjfWekWKQ
1z0A==
X-Gm-Message-State: ALoCoQlG7+bn5pSRXcMn8G0JMLIzEmSeqGLxx/4rnkR9cuVypBhjrydLPBq9w14CAsVGarHJYKMs
X-Received: by 10.194.186.178 with SMTP id fl18mr1609113wjc.83.1403619726907;
Tue, 24 Jun 2014 07:22:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.195.12.3 with HTTP; Tue, 24 Jun 2014 07:21:46 -0700 (PDT)
In-Reply-To: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
References: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 24 Jun 2014 10:21:46 -0400
Message-ID: <CAJHLa0Omiz+UhGjSKgYU7+b2YY7aN23w7o8CQntqMePFs7LkjA@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
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: 1WzRby-0002pu-8T
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 14:22:16 -0000
On Tue, Jun 24, 2014 at 9:27 AM, Mike Hearn <mike@plan99.net> wrote:
> Wallets would then be able to persist this data to disk and compete on cool visualisations for how much money you saved over time.
heh, this is a cool idea.
It also seems like it would be subject to instant inflation, as it's
unprovable, and a rational economic actor may choose to exaggerate
such numbers. It also seems collectively rational by some points of
view for all bitcoin actors to inflate this number.
At a minimum, I would either add "marketing_" to the field name
itself, or include additional comment caveats noting in BOLD language
that this field is informational, and should not be relied upon for
accounting/auditing purposes.
It just seems like a statistic that everyone has an incentive to exaggerate.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
