Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.176 as permitted sender)
	client-ip=209.85.223.176; envelope-from=lidstrom83@gmail.com;
	helo=mail-ie0-f176.google.com; 
MIME-Version: 1.0
Date: Thu, 3 Oct 2013 03:35:30 -0600
Message-ID: <CADjHg8Hh7Vm+CJpZH1-=0FsAxup7z42i2es-j2AW27OMt_SKTw@mail.gmail.com>
From: Daniel Lidstrom <lidstrom83@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=90e6ba614a761f990804e7d2e810
Subject: [Bitcoin-development] Identity protocol observation
Precedence: list

--90e6ba614a761f990804e7d2e810
Content-Type: text/plain; charset=ISO-8859-1

The location of a tx in the blockchain can be encoded in n=log2(h)+log2(t)
bits, where h is the block height, and t is the number of transactions in
the block.  Currently h~250,000 and t~500, so n~27.  A CVC phoneme encodes
~10.7 bits *, so a transaction today can be located in the blockchain with
3 of these, e.g. reb-mizvig.  This is reasonably short, readable and
memorable.

The identity protocol Jeff Garzik is working on will link a public key
fingerprint to a miner sacrifice transaction.  This tx could in turn be
uniquely described with a short name as above.  Associating this name with
the public key becomes secure once the tx is sufficiently buried in the
blockchain.  In the identity protocol, lightweight clients check the
validity of a sacrifice tx by checking that its merkle path is valid.  But
this path encodes, via the ordering of the hashes at each level, the
location of the transaction in the block, so the lightweight client can
verify the sacrifice tx's short name using only the information he already
has.

Some more random names:
vec-halhic
wom-vizpyd
guv-zussof
jog-copwug
seg-rizges
jyg-somgod
pax-synjem
zyg-zuxdyj
gid-mutdyj
rel-hyrdaj

Sources of inspiration:
urbit.org
https://en.bitcoin.it/wiki/Identity_protocol_v1

* This is somewhat restricted: I disallowed q for obvious reasons and k
because it conflicts with c, and c looks much softer and less like
Klingon.  H is allowed for the first consonant, but not the second, and x
is allowed for the last one, but not the first one.  Y is a vowel, but not
a consonant.  Maybe these weren't quite the right choices.  Paint away!

--90e6ba614a761f990804e7d2e810
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The location of a tx in the blockchain can be encoded in n=
=3Dlog2(h)+log2(t) bits, where h is the block height, and t is the number o=
f transactions in the block.=A0 Currently h~250,000 and t~500, so n~27.=A0 =
A CVC phoneme encodes ~10.7 bits *, so a transaction today can be located i=
n the blockchain with 3 of these, e.g. reb-mizvig.=A0 This is reasonably sh=
ort, readable and memorable.<br>
<br>The identity protocol Jeff Garzik is working on will link a public key =
fingerprint to a miner sacrifice transaction.=A0 This tx could in turn be u=
niquely described with a short name as above.=A0 Associating this name with=
 the public key becomes secure once the tx is sufficiently buried in the bl=
ockchain.=A0 In the identity protocol, lightweight clients check the validi=
ty of a sacrifice tx by checking that its merkle path is valid.=A0 But this=
 path encodes, via the ordering of the hashes at each level, the location o=
f the transaction in the block, so the lightweight client can verify the sa=
crifice tx&#39;s short name using only the information he already has.<br>
<br>Some more random names:<br>vec-halhic<br>wom-vizpyd<br>guv-zussof<br>jo=
g-copwug<br>seg-rizges<br>jyg-somgod<br>pax-synjem<br>zyg-zuxdyj<br>gid-mut=
dyj<br>rel-hyrdaj<br><br>Sources of inspiration:<br><a href=3D"http://urbit=
.org">urbit.org</a><br>
<a href=3D"https://en.bitcoin.it/wiki/Identity_protocol_v1">https://en.bitc=
oin.it/wiki/Identity_protocol_v1</a><br><br>* This is somewhat restricted: =
I disallowed q for obvious reasons and k because it conflicts with c, and c=
 looks much softer and less like Klingon.=A0 H is allowed for the first con=
sonant, but not the second, and x is allowed for the last one, but not the =
first one.=A0 Y is a vowel, but not a consonant.=A0 Maybe these weren&#39;t=
 quite the right choices.=A0 Paint away!<br>
</div>

--90e6ba614a761f990804e7d2e810--