Base58Check encoding: Difference between revisions

m
add ref link
(first draft)
 
m (add ref link)
Line 3:
[[Category:Checksums]]
 
The popular enconding of litlesmall and medium-sized [[:Category:Checksums|checksums]] is [[wp:base16|base16]], that is more compact tham usual base10 and is human readable... For checksums resulting in ''hash digests'' bigger tham ~100 bits, the base16 is too long: [[wp:base58|base58]] is shorter and (aswhen using good Bitcoin-alphabet-base58) preserves secure human readability. The most popular alphabet of base58 is the used in bitcoin address (see [[Bitcoin/address validation]]), so it is the "default base58 alphabet".
 
Write a program that takes a checksum (resultant hash digest) ''integer binary'' representation as argument, and converts (encode it) into base58 with the standard Bitcoin alphabet — which uses an alphabet of the characters 0 .. 9, A ..Z, a .. z, but without the four characters 0, O, I and l.
 
The ''reference algorithm'' is at [https://en.bitcoin.it/wiki/Base58Check_encoding#Base58_symbol_chart the Bitcoin's Base58Check page].
Anonymous user