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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1UPa2y-0006QE-KZ
for bitcoin-development@lists.sourceforge.net;
Tue, 09 Apr 2013 15:01:20 +0000
X-ACL-Warn:
Received: from mail-vc0-f175.google.com ([209.85.220.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UPa2t-0002tM-0U
for bitcoin-development@lists.sourceforge.net;
Tue, 09 Apr 2013 15:01:19 +0000
Received: by mail-vc0-f175.google.com with SMTP id ha12so273537vcb.6
for <bitcoin-development@lists.sourceforge.net>;
Tue, 09 Apr 2013 08:01:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-received:x-originating-ip:in-reply-to:references
:date:message-id:subject:from:to:cc:content-type:x-gm-message-state;
bh=cWFfBV0mBvCjlmems8L7VIf1t3dx18quMyPwRpTmP2E=;
b=g1njwZzknxbXxb4u7uLacEgKTTB84MCVkBGisEKjEuJNg+I0IO6Ih3FaDYqJUDdVLK
G2DiVuJsRsZe4ptuDqTbmoQNXO6nE1KsEo0UNUvu8PmbCnagNaTu/6Hlnfp0m+grObJW
f5/XIia2n8Y8Y7QdXZ6XSpNcERximfbuFdVdOzcIFTQlqrgSeSo3FW696NAS0zMWHY1I
K6yMvagj4NR6E7nHd91HIqtMthMK5hUxqMOb7pNa4K/4Wf2A+OWZmzCyC89esnJgqven
vgE2Ngk4/oO31ycEXFOaoDuxVsaC8n6cKXpzYPVYeNE+QBL0mrkkTNeGYscRGzG147A/
tAjQ==
MIME-Version: 1.0
X-Received: by 10.52.28.196 with SMTP id d4mr4643625vdh.56.1365519669337; Tue,
09 Apr 2013 08:01:09 -0700 (PDT)
Received: by 10.58.169.109 with HTTP; Tue, 9 Apr 2013 08:01:09 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <CANEZrP2B4CGwGp1BsPScyC_+DndLDMnHTzWhmhfUxQnE3bVuSA@mail.gmail.com>
References: <CA+8xBpc5iV=prakWKkNFa0O+tgyhoHxJ9Xwz6ubhPRUBf_95KA@mail.gmail.com>
<CANEZrP1EKaHbpdC6X=9mvyJHC_cvW7u5p9nqM7EwkEypAg4Xmg@mail.gmail.com>
<CA+8xBpdBDDxD46f9ugn-ueZGwMU6fnF4BheUGiiz1otOTdffEw@mail.gmail.com>
<CANEZrP2B4CGwGp1BsPScyC_+DndLDMnHTzWhmhfUxQnE3bVuSA@mail.gmail.com>
Date: Tue, 9 Apr 2013 11:01:09 -0400
Message-ID: <CA+8xBpeVW9pqyP+=b7gyeB4od1S97+rOwi=VV64v53E_GHO=FQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQm7tT/wNt4NGN8Xt0qiDDqdHVrmkwU+LeEASOio2ms4yymE3ycE4K7vS7RiwcVPsTF+IoLs
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1UPa2t-0002tM-0U
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] On-going data spam
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, 09 Apr 2013 15:01:20 -0000
On Tue, Apr 9, 2013 at 10:53 AM, Mike Hearn <mike@plan99.net> wrote:
>> However, there should be some metrics and heuristics that take care of
>> this problem. Notably the dev consensus (sans you, Mike :)) seems to
>> be that uneconomical outputs should be made non-standard.
> I think that patch is ok as it doesn't really have any fixed concept of what
> is uneconomical. But I haven't thought about it much. As Gavin says, there's
> an obvious backwards compatibility problem there. It should probably wait
> until the payment protocol work is done, so the major user of
> micropayments-as-messages can migrate off them.
"wait" is only an option if there is an alternate solution already
coded and ready for 0.8.2.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
