From: Gavin Andresen <gavinandresen@gmail•com>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] After compressed pubkeys: hybrid pubkeys
Date: Sat, 16 Jun 2012 17:41:52 -0400 [thread overview]
Message-ID: <CABsx9T1_R2RE0S=ygY18OyJ0W+Bxyt5Q75bF4J36r0C8ae4-Fw@mail.gmail.com> (raw)
In-Reply-To: <20120616192651.GA13438@vps7135.xlshosting.net>
RE: 0x06/0x07 'hybrid' public keys:
> Any opinions? Forbidding it certainly makes alternative implementation
> slightly easier in the future, but I'm not sure the hassle of a network
> rule change is worth it.
I say treat any transactions that use them as 'non-standard' -- don't
relay/mine them by default, but accept blocks that happen to contain
them.
I agree that a rule change isn't worth it right now, but making them
non-standard now is easy and should make a rule change in the future
easier.
--
--
Gavin Andresen
next prev parent reply other threads:[~2012-06-16 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 19:26 Pieter Wuille
2012-06-16 21:41 ` Gavin Andresen [this message]
2012-06-16 23:39 ` Gregory Maxwell
2012-06-17 1:15 ` Luke-Jr
2012-06-17 11:01 ` Mike Hearn
2012-06-17 12:04 ` Pieter Wuille
2012-06-17 15:16 ` Wladimir
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='CABsx9T1_R2RE0S=ygY18OyJ0W+Bxyt5Q75bF4J36r0C8ae4-Fw@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pieter.wuille@gmail$(echo .)com \
/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