3 ms·
The need for embedded some form of error correcting codes into readable keys like these is a really good point. While not the same, I'm reminded of the issue w
by codys 9y ago
The need for embedded some form of error correcting codes into readable keys like these is a really good point.
While not the same, I'm reminded of the issue with etherium addresses where they've (after initially having no extra checking) started using mixed case to provide a checksum to detect incorrect entries. Otherwise, it's really easy to send coins to a very slightly different address due to a typo.
With Saicoin, it seems like just adding 1 more word could allow correction of mistakes like these. (And you'd end up with a round 30 words :).
- sp332 9y agoIt does have a checksum. That means error-correcting works just like in the article, by picking the nearest valid code. This could be built-in to the software.
- logicallee 9y agoRather than a checksum, I think we're talking about something like a recovery record[1] or some kind of error correcting code, which is slightly different. [1] like these - https://en.wikipedia.org/wiki/Comparison_of_archive_formats#Recovery_record https://en.wikipedia.org/wiki/Comparison_of_archive_formats#...
- Taek 9y agoIt would take about 0.5 seconds of brute forcing for the library to figure out if you had gotten a word wrong, so that's actually reasonable.