summaryrefslogtreecommitdiff
path: root/49/1af71c7b80fdb7f4148cbc7126ed98b492adf8
blob: 4856100e65eef74ac6e16fd2699ced7c3a29dd93 (plain)
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
124
125
126
127
128
129
130
131
132
133
134
135
Return-Path: <cryptaxe@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 57B768F5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  6 Sep 2017 23:54:06 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f173.google.com (mail-wr0-f173.google.com
	[209.85.128.173])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B2B95124
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  6 Sep 2017 23:54:05 +0000 (UTC)
Received: by mail-wr0-f173.google.com with SMTP id a43so16401545wrc.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 06 Sep 2017 16:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=Co8rxRF71lOXO9ArK6zQ0ZfCEAnB6nKr64EjAuDHVuA=;
	b=LGRTNWkO3CZsFjZZxzqI2XX734zkQh2R0Xo5QhvN63DGPWkQsTXqBTEzjd+pNCYjNf
	Dai1ehY5YRF8TU9L37MyCtcWsI9Nc+3M/T3mBNyg2TulDug1oXQ8oFvolIdJdtdOxCdX
	H78KXkos/VUC5cxQPqfRL6NzhiTP28xUssc/SyvbZSCGxsH9EkWINbVaVjrG3uHQBkrd
	zjpGVj6Q9tcGUBBUwi+0tSgNbELU4C9n68KrEVLxeiBJkqWNQkwkmED/9c+3pOlNFt/l
	Hgp1kP+Kd9HsiIN01wWWBmzsWPGAHHc/RMYNbn/UjCaZSaM4BGaUZvGn+GVTnHV+ffK5
	s/bw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=Co8rxRF71lOXO9ArK6zQ0ZfCEAnB6nKr64EjAuDHVuA=;
	b=EyTcNEEOYVqJcoII5e5AAkCXXtKFpWM7NIjiOnnTkpXZn6CkbDmzS0DjVdzq8xCm0P
	W5s2dPi+CGQQpn/QJwxMplABxrJfvT7R48ngTRD+cLIG7eibSP6gg1tlOpBKe7WATdRM
	FbXRlF+l46z8hckgm/AgSXix3HQroPMAVrz7WZzutu1Pk+iKDF0HyVJBB+yc6dsw77yx
	oQZ3wgGD5ZFXCH3RvzctYLKIA1QD3lZBrwmDAS3KfVizHD5ZZ2z+35XCZF456Ib/w687
	rTAWAgYDjD5gibuj4KRCZfNHa9y3AjBZSYRx9saxoVOB+/IBf78iuGN4IffHdYpALy+E
	f19w==
X-Gm-Message-State: AHPjjUieeq7U6aCjjdkMuV9nSs+Bz8FagB5d3CQsz8scQVzioZIdlw9Z
	/INsJ9NmNbkki12hEuYIZv2vRpZxHA==
X-Google-Smtp-Source: ADKCNb4Gg2L9q2kfuUY0j/wyLeiY+eESVffWPRvEbuQgAjEH/3ReibLUgFYNV4h3qwJJFy1zpzzHQtTgMIPtfc7MPvM=
X-Received: by 10.223.187.211 with SMTP id z19mr428373wrg.97.1504742044293;
	Wed, 06 Sep 2017 16:54:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.217.194 with HTTP; Wed, 6 Sep 2017 16:54:03 -0700 (PDT)
Received: by 10.28.217.194 with HTTP; Wed, 6 Sep 2017 16:54:03 -0700 (PDT)
In-Reply-To: <CABm2gDojDQWMhw8wW1UkRGKtdbby2+6AFFZLPuRcUb7WF_u5qQ@mail.gmail.com>
References: <CABm2gDojDQWMhw8wW1UkRGKtdbby2+6AFFZLPuRcUb7WF_u5qQ@mail.gmail.com>
From: CryptAxe <cryptaxe@gmail.com>
Date: Wed, 6 Sep 2017 16:54:03 -0700
Message-ID: <CAF5CFkh4DWE6Ca-5LFrgkGxWgYqqJdEdv+JZ+3wp+0eTm_vqCw@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="089e0820fed80762bd05588e0f51"
X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM autolearn=disabled version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 07 Sep 2017 01:01:00 +0000
Subject: Re: [bitcoin-dev] SF proposal: prohibit unspendable outputs with
	amount=0
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 23:54:06 -0000

--089e0820fed80762bd05588e0f51
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

As long as an unspendable outputs (OP_RETURN outputs for example) with
amount=3D0 are still allowed I don't see it being an issue for anything.

On Sep 5, 2017 2:52 PM, "Jorge Tim=C3=B3n via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> This is not a priority, not very important either.
> Right now it is possible to create 0-value outputs that are spendable
> and thus stay in the utxo (potentially forever). Requiring at least 1
> satoshi per output doesn't really do much against a spam attack to the
> utxo, but I think it would be slightly better than the current
> situation.
>
> Is there any reason or use case to keep allowing spendable outputs
> with null amounts in them?
>
> If not, I'm happy to create a BIP with its code, this should be simple.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--089e0820fed80762bd05588e0f51
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">As long as an unspendable outputs (OP_RETURN outputs for =
example) with amount=3D0 are still allowed I don&#39;t see it being an issu=
e for anything.=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Sep 5, 2017 2:52 PM, &quot;Jorge Tim=C3=B3n via bitcoin-dev&qu=
ot; &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-de=
v@lists.linuxfoundation.org</a>&gt; wrote:<br type=3D"attribution"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">This is not a priority, not very important either.<b=
r>
Right now it is possible to create 0-value outputs that are spendable<br>
and thus stay in the utxo (potentially forever). Requiring at least 1<br>
satoshi per output doesn&#39;t really do much against a spam attack to the<=
br>
utxo, but I think it would be slightly better than the current<br>
situation.<br>
<br>
Is there any reason or use case to keep allowing spendable outputs<br>
with null amounts in them?<br>
<br>
If not, I&#39;m happy to create a BIP with its code, this should be simple.=
<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</blockquote></div></div>

--089e0820fed80762bd05588e0f51--