From: "Luke-Jr" <luke@dashjr•org>
To: "Jorge Timón" <timon.elviejo@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Pubkey addresses
Date: Sun, 18 Dec 2011 09:34:37 -0500 [thread overview]
Message-ID: <201112180934.38718.luke@dashjr.org> (raw)
In-Reply-To: <CAGQP0AF92xh_SSGOryTfedfPhVdjR3B7hcp9SM9t7Gj=syxs-w@mail.gmail.com>
On Sunday, December 18, 2011 9:28:36 AM Jorge Timón wrote:
> Back on topic, is actually putting the whole pub key in each output
> what you're proposing?
Yes, just like is already done for generation, since it is more efficient
*overall* for the block chain. sipa's key extraction is a MUCH better
solution, however, so if we can get that without a block chain fork, I'm
inclined to favour it.
next prev parent reply other threads:[~2011-12-18 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 6:32 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 [this message]
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
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=201112180934.38718.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=timon.elviejo@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