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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1UPZsH-0007F4-H4
for bitcoin-development@lists.sourceforge.net;
Tue, 09 Apr 2013 14:50:17 +0000
X-ACL-Warn:
Received: from mail-vc0-f178.google.com ([209.85.220.178])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UPZsF-00020W-SN
for bitcoin-development@lists.sourceforge.net;
Tue, 09 Apr 2013 14:50:17 +0000
Received: by mail-vc0-f178.google.com with SMTP id hv10so1788541vcb.23
for <bitcoin-development@lists.sourceforge.net>;
Tue, 09 Apr 2013 07:50:10 -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=1kkd0joQ80+CKBuj/bn2cuQKiiBChwjUw501EMl0Df8=;
b=Kxl5vgBBVKDy127REwLcv8Zh/dyDh35Qw2X21YsyrdWyd953NPasmRJ5MQOQ4EH7fx
Z2O3BDEo6xnJWf9h+FMoAxSkcjMcmbczUrD4LXkfA7Zd9gMsbk/m22IMUt4r8rPhC6TI
Wm1/6QZYMXKEeXV3oVbNTQCUNmTyDLGPGbr6hps7kOI06iFygVyQoTTUS8MFm7cr9MZV
rXg4LwLLiFoYWEHTllNf9MzXFwbHouWtlM7A87tkP5pbT48JN60iWhHl1s6VjEBQbmH8
wbX5UWDqSLznq35JV0ibSjR+71j8XOtTVZyzjbIOR+XTFbwkg/uSZJ2JETULHl9NdOk4
VJxA==
MIME-Version: 1.0
X-Received: by 10.220.119.200 with SMTP id a8mr19444047vcr.38.1365519010174;
Tue, 09 Apr 2013 07:50:10 -0700 (PDT)
Received: by 10.58.169.109 with HTTP; Tue, 9 Apr 2013 07:50:10 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <CANEZrP1EKaHbpdC6X=9mvyJHC_cvW7u5p9nqM7EwkEypAg4Xmg@mail.gmail.com>
References: <CA+8xBpc5iV=prakWKkNFa0O+tgyhoHxJ9Xwz6ubhPRUBf_95KA@mail.gmail.com>
<CANEZrP1EKaHbpdC6X=9mvyJHC_cvW7u5p9nqM7EwkEypAg4Xmg@mail.gmail.com>
Date: Tue, 9 Apr 2013 10:50:10 -0400
Message-ID: <CA+8xBpdBDDxD46f9ugn-ueZGwMU6fnF4BheUGiiz1otOTdffEw@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: ALoCoQmLCkH/sZRa2iABxlkSqY7CLAS/B82RG997oMTw9A/bipdRYcN9LhSeLVQvmdSg86dG77Js
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: 1UPZsF-00020W-SN
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 14:50:17 -0000
Well, I'm not fundamentally opposed to a blacklist, but it would have
to be done in a VERY open manner. I do think the community would
agree that storing big data transactions is not the primary purpose of
bitcoin.
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.
Here is one approach:
Block uneconomic UTXO creation
https://github.com/bitcoin/bitcoin/pull/2351
I would like to see at least a stopgap solution to data spam in 0.8.2,
as it is a clear and present problem.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
