Topic: Why private keys are base58 encoded? (Read 2895 times)
I chose something similar to addresses because the code was available, it had a checksum against typo's, and 51 characters seemed reasonable enough to bother with implementing something else (base64 being 48 characters with the same level of checksums).
Thanks you (everybody) for your 2 cents!
The idea is that base58 is easier for humans to type in, for example from a scratch card...
Even if a private key should never be sent out publicly, it's conceivable that one might want to have a physical copy somewhere printed or written out, like in a safe or something. In that case, it may be useful to have the same base58 encoding to make sure people don't confuse 1 and l and the like.
So, I suspect that encoding it like addresses was just as easy as any other encoding, and lets one do the same writing-down that addresses have.
So, I suspect that encoding it like addresses was just as easy as any other encoding, and lets one do the same writing-down that addresses have.
Probably mostly so it is coded like the address. It looks cool.
The first byte of key is 0x80 so begins with 5.
The first byte of key is 0x80 so begins with 5.
Playing around generation of vanity addresses, I've discovered that private keys are stored as base58 numbers, with the character "5" at the beginning.
But... why?
The reason why public keys are distributed in base58, I can understand: base58 is a kind of base64 without some conflicting characters that could be confused and taken as phising target.
But, private keys never should be cast out. So, base64 seems to be perfect for the goal, because it is the easiest way to "textify" binaries, the most compact and most universal.
For example, the private key:
In base64 (excluding the starting "5"):
Any clues for this strange election?
But... why?
The reason why public keys are distributed in base58, I can understand: base58 is a kind of base64 without some conflicting characters that could be confused and taken as phising target.
But, private keys never should be cast out. So, base64 seems to be perfect for the goal, because it is the easiest way to "textify" binaries, the most compact and most universal.
For example, the private key:
Code:
5JEiDZ747ZRjB22ie48Gq1ADUZuU2Fjw2xJE5D4LCXcK8E81zAh
In base64 (excluding the starting "5"):
Code:
I3fcciKvYeoG/mTtUnTbX1XAW4WGqrWz1Z2g7/IC1Mz/B4++G
Any clues for this strange election?
Jump to: