public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andrew Poelstra <apoelstra@wpsoftware.net>
To: Christopher Gilliard <christopher.gilliard@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF
Date: Fri, 16 Apr 2021 15:55:47 +0000	[thread overview]
Message-ID: <YHmzg15MAzHLRC5p@camus> (raw)
In-Reply-To: <CAK=nyAz5+yMUA=XDcunA1eeachSisaJoYE2_yzTLj=B0r4=w5A@mail.gmail.com>

On Fri, Apr 16, 2021 at 03:34:33PM +0000, Christopher Gilliard via bitcoin-dev wrote:
> This sounds like a good justification to remove the legacy multi-signature
> capabilities as well.
>

Doing so would confiscate coins, and also it is impossible to remove
legacy multisignatures in general without gutting almost all of Script.
 
> >> Thus, given that it is otherwise impossible to stop people from putting
> arbitrary data values into their transactions, then we rather encourage
> people who are going to encode their arbitrary data in transaction to use
> the OP_RETURN outputs in order to avoid UTXO bloat.
> 
> You can't make it completely impossible to do that, but you can make it
> harder and at the same time you can provide a solution for doing what they
> want to do.
>

I don't think you can even make it harder in a meaningful sense. There is
too much flexibility in transaction data.
 
-- 
Andrew Poelstra
Director of Research, Blockstream
Email: apoelstra at wpsoftware.net
Web:   https://www.wpsoftware.net/andrew

The sun is always shining in space
    -Justin Lewis-Webster



  reply	other threads:[~2021-04-16 15:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  7:45 [bitcoin-dev] BIP - limiting OP_RETURN / HF Christopher Gilliard
2021-04-16 13:56 ` Russell O'Connor
2021-04-16 15:34   ` Christopher Gilliard
2021-04-16 15:55     ` Andrew Poelstra [this message]
2021-04-16 23:52     ` ZmnSCPxj
2021-04-17  3:57       ` Christopher Gilliard
2021-04-17 15:50         ` Peter Todd
2021-04-17 16:57           ` Christopher Gilliard
2021-04-16 13:59 ` Clark Moody
2021-04-16 15:33   ` Christopher Gilliard
2021-04-16 16:32 ` Jeremy
2021-04-16 17:05   ` Christopher Gilliard
2021-04-16 18:00     ` Jeremy
2021-04-16 19:15 ` Kostas Karasavvas
2021-04-16 20:12   ` Christopher Gilliard
2021-04-17  7:41     ` Kostas Karasavvas
2021-04-16 20:30   ` Ruben Somsen
2021-04-16 21:09     ` Christopher Gilliard
2021-04-20  1:23     ` yanmaani
2021-04-20  8:45       ` Zach Greenwood
2021-04-20 17:12         ` Christopher Gilliard
2021-04-20 19:07       ` Ruben Somsen
2021-05-03  5:17         ` ZmnSCPxj
2021-05-04 12:51           ` Ruben Somsen
2021-04-20  1:22 ` yanmaani

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=YHmzg15MAzHLRC5p@camus \
    --to=apoelstra@wpsoftware.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=christopher.gilliard@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