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
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B9C48900
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Sep 2017 21:51:47 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ua0-f176.google.com (mail-ua0-f176.google.com
[209.85.217.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 546B5203
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 5 Sep 2017 21:51:47 +0000 (UTC)
Received: by mail-ua0-f176.google.com with SMTP id k23so10803052uaf.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 05 Sep 2017 14:51:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=jtimon-cc.20150623.gappssmtp.com; s=20150623;
h=mime-version:from:date:message-id:subject:to;
bh=yqYoctXXBBEdvoPys1wkNd4N0Y3/CzH/ReFocvEU2UU=;
b=s5CT1jtdpdATA7bKmEnMJnD37Bi/x1O6xkzLDTzN0/GOJlzJE/Oz/KWi3BUTv+P0TG
JIM1l7pQS8CLuQKS63MtM3HCbVY7f/utC5iy/sIM8lned88xnoGEDqS4TKj6xCn2CjTI
KjhMNzWQAzfx9CR4AIrCup4GDf/YmDd9AMC/ShfGIudcqS71P2ZNZWGwEVcjd+6FScyO
DjIfwix1IuKpimk2VZKvf1hZarCk6p3cp0PlEaPxW8H2hTeXlqQOxkXqzWv+QamiohhL
W8QE/7tEHX8A80CEKloAGej8+yUjjmzOQw60s5G3pD246LyToaYLyZuOnesktSZYBC+K
MUKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=yqYoctXXBBEdvoPys1wkNd4N0Y3/CzH/ReFocvEU2UU=;
b=Jz4TbESHTSkUi/LPMgsAdXiTQfiXkL57CUTqaUqbYue7S4l38K6kOh8CDaENFwilCl
EODYDuWhrc6olV9aa23RGsYJdA1g5hnTQ7UF7UEql0mbG4q6hj0DTqgRmLdh0MbIWna7
jOM0/fpjhxJZZHhhFObTVpnqH8KR+vPeMIyzsWnjwnSD624rvThRk4epYQhP9llO/c0g
MZ91fFg+KbDtLn+NXaCcDuxWmCz+ioEc+hkHpEDrHKtzJvDQFp14prhqbWPBPFRlA4Jr
PQxMPGfUMmFDm2paRlKf5Os8hS6qIBDjpsROmZEpU4XtjVYxjoUlIOiNcGSc0zVfSYCP
idKg==
X-Gm-Message-State: AHPjjUgH//VP5fWqsaXpWRF1Rp3toX8I/slR/ZbXVTlaLUfLe8VZg0pz
xW12nPFMLP0rc5Q1c/z9c6LNUcfVe1em
X-Google-Smtp-Source: ADKCNb6LlHPa80C8UCvAN9SvgK+mRvrYf5eycFdn1PHZwKbKckWCL9e6dRWUje8dFWdFV34buk81YSvaC3zQuRiW4rA=
X-Received: by 10.176.21.129 with SMTP id i1mr349151uae.142.1504648306286;
Tue, 05 Sep 2017 14:51:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.2.6 with HTTP; Tue, 5 Sep 2017 14:51:45 -0700 (PDT)
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Date: Tue, 5 Sep 2017 23:51:45 +0200
Message-ID: <CABm2gDojDQWMhw8wW1UkRGKtdbby2+6AFFZLPuRcUb7WF_u5qQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=0.5 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
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
Subject: [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: Tue, 05 Sep 2017 21:51:47 -0000
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.
|
