public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Pubkey addresses
Date: Sat, 17 Dec 2011 19:39:32 -0500	[thread overview]
Message-ID: <201112171939.33235.luke@dashjr.org> (raw)
In-Reply-To: <201112171928.13504.luke@dashjr.org>

On Saturday, December 17, 2011 7:28:12 PM Luke-Jr wrote:
> On Saturday, December 17, 2011 6:46:34 PM Gregory Maxwell wrote:
> > Sorry to be curt— I'm a little irritated that discussion on recovery
> > in OP_EVAL was dropped because "input script size doesn't matter
> > because of pruning" and now people are talking about adding another
> > address type which creates seriously bloated transactions where there
> > is pruning, because its slightly smaller in the no-pruning case (and
> > again, still not as small for key recovery).
> 
> I missed that bit. I'm willing to defer full OP_EVAL support on Eligius in
> order to enable key recovery...

In fact, as long as we have this opportunity to enable new opcodes, maybe we 
should spend some time revisiting what doors that opens...



      reply	other threads:[~2011-12-18  0:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17  6:32 [Bitcoin-development] Pubkey addresses Luke-Jr
2011-12-17 11:14 ` Jorge Timón
2011-12-17 16:15   ` Matt Corallo
2011-12-17 18:20     ` Jordan Mack
2011-12-18 12:15       ` Jorge Timón
2011-12-18 14:03         ` Luke-Jr
2011-12-18 14:28           ` Jorge Timón
2011-12-18 14:34             ` Luke-Jr
2011-12-18 15:42         ` Pieter Wuille
2011-12-18 19:50           ` Jorge Timón
2011-12-17 13:54 ` Wladimir
2011-12-17 21:52 ` Luke-Jr
2011-12-17 23:46   ` Gregory Maxwell
2011-12-18  0:28     ` Luke-Jr
2011-12-18  0:39       ` Luke-Jr [this message]

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=201112171939.33235.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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