From: Jim Paris <jim@jtan.com>
To: Mark Friedenbach <mark@monetize.io>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Base-32 error correction coding
Date: Mon, 24 Feb 2014 13:29:31 -0500 [thread overview]
Message-ID: <20140224182931.GA16588@psychosis.jim.sh> (raw)
In-Reply-To: <5306BCC1.8040004@monetize.io>
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
prev parent reply other threads:[~2014-02-24 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 2:41 [Bitcoin-development] Base-32 error correction coding Mark Friedenbach
2014-02-24 18:29 ` Jim Paris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140224182931.GA16588@psychosis.jim.sh \
--to=jim@jtan.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mark@monetize.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox