I want to have a physical copy of my secret data, but I don't trust printers, so I want to write it down by hand. It's a lot to write down as is, so I suggest that paperkey supports base58 as an alternative to the raw and base16 outputs. Base58 is similar to base64, except that the following characters are not used to prevent ambiguity: plus (+), slash (/), zero (0), capital i (I), capital o (O), and lowercase L (l). This encoding is almost 1.5x as space-efficient as base16, which already saves quite a bit of writing. (It took me over two hours to write down my key in base16, because I wrote very carefully to make it was legible.) It might be necessary to use longer CRC codes per line as the entropy per line has significantly increased.
I want to have a physical copy of my secret data, but I don't trust printers, so I want to write it down by hand. It's a lot to write down as is, so I suggest that paperkey supports base58 as an alternative to the
rawandbase16outputs. Base58 is similar to base64, except that the following characters are not used to prevent ambiguity: plus (+), slash (/), zero (0), capital i (I), capital o (O), and lowercase L (l). This encoding is almost 1.5x as space-efficient as base16, which already saves quite a bit of writing. (It took me over two hours to write down my key in base16, because I wrote very carefully to make it was legible.) It might be necessary to use longer CRC codes per line as the entropy per line has significantly increased.