From: "Jorge Timón" <jtimon@jtimon.cc>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] SF proposal: prohibit unspendable outputs with amount=0
Date: Tue, 5 Sep 2017 23:51:45 +0200 [thread overview]
Message-ID: <CABm2gDojDQWMhw8wW1UkRGKtdbby2+6AFFZLPuRcUb7WF_u5qQ@mail.gmail.com> (raw)
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.
next reply other threads:[~2017-09-05 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 21:51 Jorge Timón [this message]
2017-09-06 22:20 ` [bitcoin-dev] SF proposal: prohibit unspendable outputs with amount=0 Tier Nolan
2017-09-06 23:54 ` CryptAxe
2017-09-07 1:29 ` Adam Back
2017-09-07 3:41 ` CryptAxe
2017-09-07 9:56 ` Hampus Sjöberg
2017-09-07 10:31 ` Tier Nolan
2017-09-07 18:00 ` Peter Todd
2017-09-09 21:11 ` Jorge Timón
2017-09-13 9:24 ` Peter Todd
2017-09-13 9:34 ` Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABm2gDojDQWMhw8wW1UkRGKtdbby2+6AFFZLPuRcUb7WF_u5qQ@mail.gmail.com \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox