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 <peter@coinlab.com>) id 1SZOTq-00029t-DZ for bitcoin-development@lists.sourceforge.net; Tue, 29 May 2012 15:37:06 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of coinlab.com designates 209.85.210.47 as permitted sender) client-ip=209.85.210.47; envelope-from=peter@coinlab.com; helo=mail-pz0-f47.google.com; Received: from mail-pz0-f47.google.com ([209.85.210.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1SZOTk-0005Ye-KZ for bitcoin-development@lists.sourceforge.net; Tue, 29 May 2012 15:37:06 +0000 Received: by dalh21 with SMTP id h21so5487160dal.34 for <bitcoin-development@lists.sourceforge.net>; Tue, 29 May 2012 08:36:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=3x3/bn/bMvGTCcbXLUL15MM121iYhIath5/HZ5Rke0U=; b=KvydTYq96o2OikTz0YaaxL57hVhJ4TZqcl+OlCGlvOKjedVlRtq7OIEzOnDh22YeHg iIHiQNh2iJi6acOOsWZbPkmb6j4M+87Doz2/ZYkdIPrkT7v+TwOoMQ18883JbHjPeYIS 5IP0F12hq3iZB70BJmN9R4VDyMkWuReye2EMdk2283jBG9ubfBoew+foGLxHlXepxAWz /J5bCDsQUgv7IemHAZ/z+ZegSxOrxF8LvBMA5Cy5/f2EW3G5quwKC+u+yWo56aSFHDu9 GpSoiQfMFfkhGBfa3uhFOszYG7qHT7ZEe+9tYdKoDwYuRiRP3Mzne1hxHRvUpQNkjaJ5 DpMg== Received: by 10.68.201.136 with SMTP id ka8mr14439710pbc.124.1338305814441; Tue, 29 May 2012 08:36:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.13.1 with HTTP; Tue, 29 May 2012 08:36:34 -0700 (PDT) In-Reply-To: <201205291534.40364.luke@dashjr.org> References: <CA+8xBpdBe4yR6xkCODL6JQ41Gyx9eWcGGGvcQVt7DCmaEnAhbg@mail.gmail.com> <201205291518.56618.luke@dashjr.org> <CAMGNxUvWZziLppNoqntKgLVmBs_H1Ka_qH6qUtYskJovx5HgiA@mail.gmail.com> <201205291534.40364.luke@dashjr.org> From: Peter Vessenes <peter@coinlab.com> Date: Tue, 29 May 2012 11:36:34 -0400 Message-ID: <CAMGNxUtMmrT=J+SwpZvT0n-Uj_LoRuMwbEx10PoJo2BvfLFacA@mail.gmail.com> To: Luke-Jr <luke@dashjr.org> Content-Type: multipart/alternative; boundary=e89a8fb20784abad6704c12e9a56 X-Gm-Message-State: ALoCoQkbgsj2TL38L8NrS2209hOK66bEoUho5CCOkzsq10JxoG4kIu/g7lyPiaKa/nhBQQIykAIa X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 1.0 HTML_IMAGE_ONLY_16 BODY: HTML: images with 1200-1600 bytes of words 0.0 T_REMOTE_IMAGE Message contains an external image -0.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SZOTk-0005Ye-KZ Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Punishing empty blocks? 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: Tue, 29 May 2012 15:37:06 -0000 --e89a8fb20784abad6704c12e9a56 Content-Type: text/plain; charset=ISO-8859-1 I suppose I mean that I don't understand how to reverse that into a URL when one is presented only with a block, or perhaps a coinbase in a transaction. Best, Peter On Tue, May 29, 2012 at 11:34 AM, Luke-Jr <luke@dashjr.org> wrote: > On Tuesday, May 29, 2012 3:28:56 PM Peter Vessenes wrote: > > I don't understand what the 20 byte keyhash is. Can you elucidate? > > 20 byte keyhashes are a fundamental building block of the Bitcoin protocol. > > ripemd160(sha256(ecdsaPubKey)) > -- Peter J. Vessenes CEO, CoinLab M: 206.595.9839 Skype: vessenes Google+ <https://plus.google.com/112885659993091300749> --e89a8fb20784abad6704c12e9a56 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I suppose I mean that I don't understand how to reverse that into a URL= when one is presented only with a block, or perhaps a coinbase in a transa= ction.<div><br></div><div>Best,</div><div><br></div><div>Peter<br><br><div = class=3D"gmail_quote"> On Tue, May 29, 2012 at 11:34 AM, Luke-Jr <span dir=3D"ltr"><<a href=3D"= mailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>></span> wr= ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border= -left:1px #ccc solid;padding-left:1ex"> <div class=3D"im">On Tuesday, May 29, 2012 3:28:56 PM Peter Vessenes wrote:= <br> > I don't understand what the 20 byte keyhash is. Can you elucidate?= <br> <br> </div>20 byte keyhashes are a fundamental building block of the Bitcoin pro= tocol.<br> <br> ripemd160(sha256(ecdsaPubKey))<br> </blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><table style= =3D"font-family:Times"><tbody><tr><td><img src=3D"http://coinlab.com/images= /coinlab-logo.png"></td><td valign=3D"bottom"><div style=3D"font-family:Rob= otoLight,'Lucida Grande',Helmet,Freesans,sans-serif;font-size:16px;= line-height:20px"> Peter J. Vessenes<br>CEO, CoinLab<br>M: 206.595.9839<br>Skype: vessenes<br>= <a href=3D"https://plus.google.com/112885659993091300749" target=3D"_blank"= >Google+</a></div></td></tr></tbody></table><br> </div> --e89a8fb20784abad6704c12e9a56--