Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 57B768F5 for ; 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 ; Wed, 6 Sep 2017 23:54:05 +0000 (UTC) Received: by mail-wr0-f173.google.com with SMTP id a43so16401545wrc.0 for ; 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: References: From: CryptAxe Date: Wed, 6 Sep 2017 16:54:03 -0700 Message-ID: To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= , Bitcoin Protocol Discussion 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
As long as an unspendable outputs (OP_RETURN outputs for = example) with amount=3D0 are still allowed I don't see it being an issu= e for anything.=C2=A0

On Sep 5, 2017 2:52 PM, "Jorge Tim=C3=B3n via bitcoin-dev&qu= ot; <bitcoin-de= v@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<= br> 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--