From: Andy Parkins <andyparkins@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP16/17 replacement
Date: Wed, 1 Feb 2012 09:48:13 +0000 [thread overview]
Message-ID: <201202010948.13169.andyparkins@gmail.com> (raw)
In-Reply-To: <201201311158.50801.luke@dashjr.org>
[-- Attachment #1: Type: Text/Plain, Size: 516 bytes --]
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().
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 9:48 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 [this message]
2012-02-01 10:02 ` Pieter Wuille
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=201202010948.13169.andyparkins@gmail.com \
--to=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