public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: Toby Padilla <tobypadilla@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP Draft] Allow zero value OP_RETURN in Payment Protocol
Date: Tue, 26 Jan 2016 03:23:13 +0000	[thread overview]
Message-ID: <201601260323.14993.luke@dashjr.org> (raw)
In-Reply-To: <CAGcHOzw88za1m6uJY9MBO2X=3psNk667FyBOHz2XCPO3ABbcRw@mail.gmail.com>

On Tuesday, January 26, 2016 3:17:12 AM Toby Padilla wrote:
> I don't think every application of OP_RETURN could be classified as "spam".

Perhaps not, but in this context I cannot think of any non-spam use cases.
Use cases should come before changes to support them.

> I also don't think burning the value is going to dissuade anyone from going
> down that route. I don't think lost value is better for anyone.

Lost value is better because it has a cost to the spammer, and deflates the 
rest of the bitcoins.

Luke


  reply	other threads:[~2016-01-26  3:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  1:02 [bitcoin-dev] [BIP Draft] Allow zero value OP_RETURN in Payment Protocol Toby Padilla
2016-01-26  2:24 ` Luke Dashjr
2016-01-26  2:54   ` Toby Padilla
2016-01-26  2:56     ` Luke Dashjr
2016-01-26  3:01       ` Toby Padilla
2016-01-26  3:04         ` Luke Dashjr
2016-01-26  3:07           ` Toby Padilla
2016-01-26  3:12             ` Luke Dashjr
2016-01-26  3:17               ` Toby Padilla
2016-01-26  3:23                 ` Luke Dashjr [this message]
2016-01-26  3:30                   ` Toby Padilla
2016-01-26 16:19                     ` Thomas Kerin
2016-01-26 17:44                       ` Toby Padilla
2016-02-02 17:03                         ` Peter Todd
2016-02-02 17:16                           ` Pieter Wuille
2016-02-02 17:27                             ` Toby Padilla
2016-02-02 17:38                               ` Peter Todd
2016-02-02 17:41                                 ` Toby Padilla
2016-02-02 19:12                                   ` Peter Todd
2016-02-02 19:22                                     ` Toby Padilla
2016-02-02 19:14                             ` Luke Dashjr
2016-01-26 14:37     ` Andreas Schildbach
2016-01-26 17:41       ` Toby Padilla
2016-02-02 17:07         ` Peter Todd

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=201601260323.14993.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=tobypadilla@gmail.com \
    /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