From: Andy Parkins <andyparkins@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP16/17 replacement
Date: Wed, 1 Feb 2012 10:25:19 +0000 [thread overview]
Message-ID: <201202011025.19771.andyparkins@gmail.com> (raw)
In-Reply-To: <CAPg+sBgkEd71CUGHooymeVwGkz5axZMOck5o-nic8TM706T8OQ@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 669 bytes --]
On 2012 February 01 Wednesday, Pieter Wuille wrote:
> > 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.
Ah. My misunderstanding then.
> 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.
That makes a big difference. Thanks for the correction.
Andy
--
Dr Andy Parkins
andyparkins@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-01 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:50 [Bitcoin-development] BIP16/17 replacement 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 [this message]
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=201202011025.19771.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pieter.wuille@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