From: Gregory Maxwell <gmaxwell@gmail•com>
To: Andy Parkins <andyparkins@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP16/17 replacement
Date: Tue, 31 Jan 2012 12:45:14 -0500 [thread overview]
Message-ID: <CAAS2fgTvvDT+acJQfwAGpVNeA2PAQ7wip9xXc-__V2oz-=Kk6Q@mail.gmail.com> (raw)
In-Reply-To: <201201311651.02726.andyparkins@gmail.com>
On Tue, Jan 31, 2012 at 11:50 AM, Andy Parkins <andyparkins@gmail•com> wrote:
> Hello,
>
> Gulp. Am a little nervous about wading into this swamp. However, it seems
> to me that the debate has veered into the personal and away from the
I think you've been deceived by people who have some interest in
promoting this as some sort of big controversy, or perhaps just
confused by the general level of noise.
The differences between BIP16/BIP17 are technically obscure, everyone
who is well versed in the issue (with the potential exception of
Luke). There is broad consensus among the involved technically minded
parties over just about all of it.
Luke has been maintaining an opinion tracker page:
https://en.bitcoin.it/wiki/P2SH_Votes
reflecting the views of core developers and people who've been
technically involved enough to have an informed opinion.
> Surely if there are objections to both suggestions, that another
> solution might be better?
There is always a different color that the shed could be painted.
Expecting absolute consensus on the _best_ way forward is an
unreasonable standard, especially if you're going to invite the
opinions of many people.
Depending on how you count we have considered a good two dozen options
in this space— Starting with the OP_CAT key combinations many months
back, and including many variants of the current ideas. The BIPs only
represent the "final" surviving ideas.
In particular, BIP16 was the isolated consensus path forward that came
out of the discussions about the concerns that BIP12 was too
computationally powerful— I don't think I can identify any particular
person as the author of the BIP16 idea. At the the time BIP16 became
a BIP only Luke was actively objecting to it.
Though his hard work and tireless (...unstoppable dogmatic) promotion
he's managed to build a workable alternative, and it now has some
support other than himself. This, however, doesn't constitute a
material schism.
> this idea up for my traditional mailing-list roasting but with the hope that
As always, asbestos underwear is required.
> If the change is going to be a big one anyway and will require a client
> upgrade why not...
It does not, in fact— Yes, it requires a client update to make use of
the new functionality, but old nodes will happily continue to validate
things. It's hard to express how critical this is distinctly.
Bitcoin is, predominantly, a zero-trust system. Nodes don't trust that
things were done right, the validate them for themselves.
A breaking change of the kind you suggest is not something that would
be considered lightly, and this is certainly not justified for this.
> - Increase the version number in transactions to make a new transaction
> structure
> - Dump the "scriptPubKey" field completely. Everything will be pay-to-
> script-hash in version2 transactions
> - Replace it with "hashOfClaimingScript"
> - Add an "unsignedParameters" array.
If we ever were to scrap the system, I think we very much would do
something like what you describe here... and as much has been
documented:
https://en.bitcoin.it/wiki/Hardfork_Wishlist
(see "Elimination of output scripts")
But, to be clear, this stuff is pretty much fantasy. I'm doubtful that
it will ever happen, doubtful that we can get the kind of development
resources required to pull off a true breaking change in a way that
people would actually trust upgrading to— at least not before a time
that the system is simply too big to make that kind of change.
next prev parent reply other threads:[~2012-01-31 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:50 Andy Parkins
2012-01-31 16:58 ` Luke-Jr
2012-01-31 17:11 ` Andy Parkins
2012-02-01 9:48 ` Andy Parkins
2012-02-01 10:02 ` Pieter Wuille
2012-02-01 10:25 ` Andy Parkins
2012-01-31 17:45 ` Gregory Maxwell [this message]
2012-02-01 9:46 ` Andy Parkins
2012-02-01 14:14 ` Andy Parkins
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='CAAS2fgTvvDT+acJQfwAGpVNeA2PAQ7wip9xXc-__V2oz-=Kk6Q@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=andyparkins@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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