This should make it compatible with Namecoin addresses... Here's a revised proposal: * Bits 128/64 define network class ** 0 = main network ** 64,128 = reserved ** 192 = test network * Bits 32/16 define network ** 0 = Bitcoin ** 16 = reserved ** 32 = OTHER (next octet) ** 48 = Namecoin
The rest is left up to the network to decide; for Bitcoin, it is: * Bits 8/4/2 define data class ** 0 = Public key hash ** 2 = reserved ** 4 = Script hash ** 6 = Public key (raw) ** 8 = Signature ** 10 = reserved ** 12 = Private key (raw) ** 14 = OTHER (next octet) * Bit 1 is freely chosen (for aesthetic assignment) ------------------------------------------------------------------------------ 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
