diff options
| author | Luke-Jr <luke@dashjr.org> | 2011-12-17 19:28:12 -0500 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2011-12-18 00:28:33 +0000 |
| commit | 90f84c0ddf823d2fca9b9eca36eda5b0396b7c46 (patch) | |
| tree | 210556535b0433fd7846d2a0a4a3b14f4051cddd /7a/e89f879da89e09d92f4e27db06fa4b1ddf5d5c | |
| parent | 7c17dfc066c9fa0de6cb0835c0800a8d1a50b4c1 (diff) | |
| download | pi-bitcoindev-90f84c0ddf823d2fca9b9eca36eda5b0396b7c46.tar.gz pi-bitcoindev-90f84c0ddf823d2fca9b9eca36eda5b0396b7c46.zip | |
Re: [Bitcoin-development] Pubkey addresses
Diffstat (limited to '7a/e89f879da89e09d92f4e27db06fa4b1ddf5d5c')
| -rw-r--r-- | 7a/e89f879da89e09d92f4e27db06fa4b1ddf5d5c | 66 |
1 files changed, 66 insertions, 0 deletions
diff --git a/7a/e89f879da89e09d92f4e27db06fa4b1ddf5d5c b/7a/e89f879da89e09d92f4e27db06fa4b1ddf5d5c new file mode 100644 index 000000000..1d4f980af --- /dev/null +++ b/7a/e89f879da89e09d92f4e27db06fa4b1ddf5d5c @@ -0,0 +1,66 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <luke@dashjr.org>) id 1Rc4cD-00038D-4v + for bitcoin-development@lists.sourceforge.net; + Sun, 18 Dec 2011 00:28:33 +0000 +X-ACL-Warn: +Received: from zinan.dashjr.org ([173.242.112.54]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1Rc4cC-0006QJ-AS for bitcoin-development@lists.sourceforge.net; + Sun, 18 Dec 2011 00:28:33 +0000 +Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net + [184.4.160.40]) (Authenticated sender: luke-jr) + by zinan.dashjr.org (Postfix) with ESMTPSA id 3260956054D; + Sun, 18 Dec 2011 00:28:26 +0000 (UTC) +From: "Luke-Jr" <luke@dashjr.org> +To: Gregory Maxwell <gmaxwell@gmail.com> +Date: Sat, 17 Dec 2011 19:28:12 -0500 +User-Agent: KMail/1.13.7 (Linux/3.1.4-gentoo; KDE/4.7.3; x86_64; ; ) +References: <201112170132.26201.luke@dashjr.org> + <201112171652.22148.luke@dashjr.org> + <CAAS2fgSjbkS03x+e21pRvA9jswy7OdKP4Qe3uBLe_kTbBdv77g@mail.gmail.com> +In-Reply-To: <CAAS2fgSjbkS03x+e21pRvA9jswy7OdKP4Qe3uBLe_kTbBdv77g@mail.gmail.com> +X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 +X-PGP-Key-ID: 665FC11DD53E9583 +X-PGP-Keyserver: x-hkp://subkeys.pgp.net +MIME-Version: 1.0 +Content-Type: Text/Plain; + charset="utf-8" +Content-Transfer-Encoding: quoted-printable +Message-Id: <201112171928.13504.luke@dashjr.org> +X-Spam-Score: -2.1 (--) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -2.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay + domain 0.1 AWL AWL: From: address is in the auto white-list +X-Headers-End: 1Rc4cC-0006QJ-AS +Cc: bitcoin-development@lists.sourceforge.net +Subject: Re: [Bitcoin-development] Pubkey addresses +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Sun, 18 Dec 2011 00:28:33 -0000 + +On Saturday, December 17, 2011 6:46:34 PM Gregory Maxwell wrote: +> Sorry to be curt=E2=80=94 I'm a little irritated that discussion on recov= +ery +> 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= +=20 +order to enable key recovery... + + |