From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RberU-0002p2-IC for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 20:58:36 +0000 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; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RberT-0005DU-Su for bitcoin-development@lists.sourceforge.net; Fri, 16 Dec 2011 20:58:36 +0000 Received: by wgbds1 with SMTP id ds1so6209143wgb.10 for ; Fri, 16 Dec 2011 12:58:29 -0800 (PST) Received: by 10.227.57.141 with SMTP id c13mr6702431wbh.25.1324069109695; Fri, 16 Dec 2011 12:58:29 -0800 (PST) Received: from grissom.localnet ([91.84.15.31]) by mx.google.com with ESMTPS id hq5sm14611844wib.7.2011.12.16.12.58.27 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Dec 2011 12:58:28 -0800 (PST) From: Andy Parkins 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> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112162058.28195.andyparkins@gmail.com> X-Spam-Score: -1.6 (-) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (andyparkins[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1RberT-0005DU-Su Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2011 20:58:36 -0000 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