From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP16/17 replacement
Date: Tue, 31 Jan 2012 11:58:49 -0500 [thread overview]
Message-ID: <201201311158.50801.luke@dashjr.org> (raw)
In-Reply-To: <201201311651.02726.andyparkins@gmail.com>
On Tuesday, January 31, 2012 11:50:58 AM Andy Parkins wrote:
> 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
> technical. Surely if there are objections to both suggestions, that
> another solution might be better? The answer doesn't have to be A or B,
> if the answer C turns out to be acceptable.
I'm not aware of any remaining *tangible* objections to BIP 17 at this point
(Gavin seems concerned over a theoretical risk-that-nobody-has-thought-of),
but if there's a better solution, I'm perfectly fine Withdrawing BIP 17 to
support it.
> If the change is going to be a big one anyway and will require a client
> upgrade why not...
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 said, it's
quite possible to rewrite the practical implications of both BIP 16 and 17 in
the format you seem to be suggesting. Doing so would even get rid of one of
the major objections to BIP 16 (its inconsistency).
next prev parent reply other threads:[~2012-01-31 16:59 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 [this message]
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
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=201201311158.50801.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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