Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=andyparkins@gmail.com;
	helo=mail-ww0-f53.google.com; 
From: Andy Parkins <andyparkins@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 16 Dec 2011 20:58:27 +0000
User-Agent: KMail/1.13.7 (Linux/3.0.0-1-686-pae; KDE/4.6.4; i686; ; )
References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
	<1324060177.10146.YahooMailNeo@web121006.mail.ne1.yahoo.com>
	<CABsx9T0pP4Wsxy0yMJTA0OSJY3EfeFQvqczfMdvu=j1iQmooag@mail.gmail.com>
In-Reply-To: <CABsx9T0pP4Wsxy0yMJTA0OSJY3EfeFQvqczfMdvu=j1iQmooag@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201112162058.28195.andyparkins@gmail.com>
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
Precedence: list

On Friday 16 Dec 2011 19:06:52 Gavin Andresen wrote:

> I think there is also a huge public relations benefit to using a
> standard like IIBAN instead of inventing our own. Having a Bitcoin
> Payment Routing Address (or whatever it ends up being called) that
> looks like the number issues by big financial institutions will give
> people the warm fuzzies.

I can see the PR advantages, but isn't mapping from one massively long, 
multi-character, human-opaque number (IBAN) to another (bitcoin address) a 
bit of a waste of time?

Surely the point of all this is to provide at least the possibility of a 
human-readable name for a bitcoin-address?

Isn't there a possibility that one day we might want to be able to say "send 
me those bitcoins you owe me to bitcoin.yahoo.co.uk/andyparkins"?  Or 
similar?


Andy
-- 
Dr Andy Parkins
andyparkins@gmail.com