Mark Friedenbach wrote: > What follows is a proposed BIP for human-friendly base-32 > serialization with error correction encoding. ... > 2. Automatic correction of up to 1 transcription error per 31 coded > digits (130 bits of payload data). For a 256-bit hash or secret key, > this enables seamless recovery from up to two transcription errors so > long as they occur in separate halves of the coded representation.
Can we do better than correcting single transcription errors? I'd imagine that transposition of two adjacent characters, or insertion or deletion of a single character, would be very common. At the very least, a transposition could be corrected by interleaving the two "halves of the coded representation", e.g.: ABABABABABABABABABABABABABABABABABABABABABABABABABABABABABABAB insead of AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB Jim ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
