From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] After compressed pubkeys: hybrid pubkeys
Date: Sun, 17 Jun 2012 01:15:54 +0000 [thread overview]
Message-ID: <201206170115.56502.luke@dashjr.org> (raw)
In-Reply-To: <CAAS2fgT=eLweqpmRGonuvEYfiGi4nbaKh-uw01PKyMC3qyY71A@mail.gmail.com>
On Saturday, June 16, 2012 11:39:00 PM Gregory Maxwell wrote:
> On Sat, Jun 16, 2012 at 5:41 PM, Gavin Andresen <gavinandresen@gmail•com>
wrote:
> > 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.
>
> ACK. Hopefully no one will mine these before we can merge denying
> them into another rule change. But if they do, oh well.
I'm willing to make Eligius reject these as well, if someone provides a patch
that doesn't depend on IsStandard being enforced...
Same goes for rejecting OP_NOP<n> - I can't see any legitimate reason we'd
want these on mainnet right now.
Luke
next prev parent reply other threads:[~2012-06-17 1:16 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
2012-06-16 23:39 ` Gregory Maxwell
2012-06-17 1:15 ` Luke-Jr [this message]
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=201206170115.56502.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