Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <nadav@shesek.info>) id 1Uq87I-0005bg-IZ
	for bitcoin-development@lists.sourceforge.net;
	Fri, 21 Jun 2013 20:39:32 +0000
X-ACL-Warn: 
Received: from mail-ve0-f180.google.com ([209.85.128.180])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Uq87G-0007eO-Qq
	for bitcoin-development@lists.sourceforge.net;
	Fri, 21 Jun 2013 20:39:32 +0000
Received: by mail-ve0-f180.google.com with SMTP id pa12so6906493veb.11
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 21 Jun 2013 13:39:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:from:date:message-id:subject:to
	:content-type:x-gm-message-state;
	bh=Ee3NZg7mqFZQ/eG8hibHeIbn0I8442yfbFZjZP2J8hs=;
	b=VP3jDd+354iTFoikqISuXLH05fk8svfNa4o8Ad2d6U9QZG7limp/nm0frfV+C6ATBL
	pzNK40D43ittpxAH/XNdVJTvn/QpgyNXYwCVwyDV9vd6iVtFhCD4W0WoL08n6XpIER4r
	4HN6e6vavFL4RdtFoSuqGWVBZRW+aiviq3alD2lh/upxBtKjLSdcE2FOTjBO0bYfZxic
	ZWrLaP9i16qZ8hp+D3/nKl0yO+3svoXK5OwwDe+Nrkq3Z/6DFWICvNWuG5JwZbZhdz7l
	WcqhVtWbqXb4IfkuOl7fPSxpwtFwKjHOz1ss1FrHbmlGCnnEa4/ZDAmfMSq8k+vbrq49
	6/Pg==
X-Received: by 10.220.191.129 with SMTP id dm1mr6274361vcb.54.1371845776062;
	Fri, 21 Jun 2013 13:16:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.36.177 with HTTP; Fri, 21 Jun 2013 13:15:55 -0700 (PDT)
X-Originating-IP: [217.132.7.235]
From: Nadav Ivgi <nadav@shesek.info>
Date: Fri, 21 Jun 2013 23:15:55 +0300
Message-ID: <CAGXD5f1sOBT7qZdVvyTFLDRu5Bn4BfpWgm=aQi-=M=UMnrSCCg@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=089e0115f91c2b4f8504dfafbcf9
X-Gm-Message-State: ALoCoQkKqgYJmwUtaSLdLGGd1FSNFJtI48eUCYJKMXtLmrJzF3e2u79bTu7514zEmc76nADRF+RY
X-Spam-Score: 1.1 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
X-Headers-End: 1Uq87G-0007eO-Qq
Subject: [Bitcoin-development] Standard public key base58-check address
	prefix?
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: Fri, 21 Jun 2013 20:39:32 -0000

--089e0115f91c2b4f8504dfafbcf9
Content-Type: text/plain; charset=ISO-8859-1

I'm working on a project that requires users to exchange public keys (for
multisig transactions).

It seems that hex encoding is usually used to display public keys (i.e. in
bitaddress and brainwallet), which results in longer strings and lacks the
4-bytes verification.

A standard way to encode public keys as base58-check addresses would make
it easier and safer to display and exchange public keys. All that is really
needed is deciding on a prefix byte.

Perhaps we can use 0x37/0x38, which results in the letter P (for "Public")?
It seems like those bytes aren't used for anything yet.

Thanks,
Nadav

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

<div dir=3D"ltr"><div style>I&#39;m working on a project that requires user=
s to exchange public keys (for multisig transactions).</div><div style><br>=
</div><div style>It seems that hex encoding is usually used to display publ=
ic keys (i.e. in bitaddress and brainwallet), which results in longer strin=
gs and lacks the 4-bytes verification.</div>

<div style><br></div><div style>A standard way to encode public keys as bas=
e58-check addresses would make it easier and safer to display and exchange =
public keys. All that is really needed is deciding on a prefix byte.</div>

<div style><br></div><div style>Perhaps we can use 0x37/0x38, which results=
 in the letter P (for &quot;Public&quot;)? It seems like those bytes aren&#=
39;t used for anything yet.</div><div style><br></div><div style>Thanks,</d=
iv>

<div style>Nadav</div></div>

--089e0115f91c2b4f8504dfafbcf9--