From: Pieter Wuille <pieter.wuille@gmail•com>
To: Andy Parkins <andyparkins@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP16/17 replacement
Date: Wed, 1 Feb 2012 11:02:08 +0100 [thread overview]
Message-ID: <CAPg+sBgkEd71CUGHooymeVwGkz5axZMOck5o-nic8TM706T8OQ@mail.gmail.com> (raw)
In-Reply-To: <201202010948.13169.andyparkins@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Op 1 feb. 2012 10:48 schreef "Andy Parkins" <andyparkins@gmail•com> het
volgende:
>
> On 2012 January 31 Tuesday, Luke-Jr wrote:
>
> > Both BIP 16 and 17 are backward compatible enough that people can
continue
> > to use the old clients with each other. An upgrade is only required to
> > send to (or create/receive on) the new 3...-form addresses. That being
>
> Is that true? (I'm happy to be called wrong)
>
> It doesn't seem like it to me. The new transaction types will be
rejected by
> old clients won't they? They don't pass IsStandard().
IsStandard() is for accepting transactions into the memory pool.
Non-standard transactions are verified just fine when they are in the block
chain.
BIP16/17 both create transactions that, when interpreted as old scripts,
are valid. The only change to the protocol is that previously-valid
transactions become invalid. As long as a supermajority of miners enforce
the new rules, everyone can happily keep using their old bitcoin client.
They won't create the new transaction type, and don't accept them as
payment, but they will accept the new block chain.
If we do a breaking change to the protocol - such as adding a new
transaction type - ALL users must upgrade. Those who don't will see a fork
of the chain from before the first new-style transaction. That is not the
case now.
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1586 bytes --]
next prev parent reply other threads:[~2012-02-01 10:02 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 [this message]
2012-02-01 10:25 ` Andy Parkins
2012-01-31 17:45 ` Gregory Maxwell
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=CAPg+sBgkEd71CUGHooymeVwGkz5axZMOck5o-nic8TM706T8OQ@mail.gmail.com \
--to=pieter.wuille@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