First: everybody please try to focus on the issues/ideas, and try to avoid this becoming a flame war.
Second: I think Walter Stanish made several good points that may have been missed in all the long posts and discussion, the main one being: The banking industry has been dealing with many of these issues for years; I think we should not dismiss their experience. 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 don't really care what happens behind the scenes, as long as it is as secure as an HTTPS connection (RE: CA pwnage: there's no such thing as perfect security, and until a more secure solution comes along HTTPS is the best we've got). And I'll reiterate that there doesn't have to be just one solution. My only concern is that IIBAN is Yet Another Fledgling Standard, and those little details that remain to be worked out could take years to actually work out. -- -- Gavin Andresen ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
