📅 Original date posted:2014-01-21
📝 Original message:MultiBit here.
>At least Trezor and bitcoinj (Multibit) seems to be going in this way,
>which is 100% of clients which expressed interest in bip39 :-).
>
>slush
We'll be using the BIP39 implementation present in Bitcoinj as slush says.
>Proper Unicode handling is a serious issue however. You don't want
>someone to move from one input method / machine to another and
>suddenly find that their coins are inaccessible, because of an issue
>of decomposed vs. compatibility forms or whatever.
We generate the word list internally (12,18,24) and confirm it is entered
correctly through a retyping operation. This will allow us to detect
character encoding transpositions (e.g. u0032 vs u00a0) and alert the user
before it becomes an issue.
While English is the language of the first word list to be implemented, we
would definitely integrate alternative non-English word lists to make life
easier for the global community. In general the approach would be for the
user to select their language (implying a locale) and then the word list to
be selected from that locale if available with a fallback to English. This
follows the same approach as resource bundles in Java.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140121/c576faef/attachment.html>;
Gary Rowe [ARCHIVE] /
npub1j8…wpach
2023-06-07 15:12:25
in reply to nevent1q…6ztj
Author Public Key
npub1j8mfekhmgtne6ptzxptudrcpwd6wtyxk64qdn3swy2nv46zuledskwpachSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:12:25Event JSON
{
"id": "8869350f42ce4efcf6eebe65f0f1bca33ef4de0f8374345f992159e2150d9366",
"pubkey": "91f69cdafb42e79d05623057c68f017374e590d6d540d9c60e22a6cae85cfe5b",
"created_at": 1686150745,
"kind": 1,
"tags": [
[
"e",
"fc93117f98479f5d69e7743f0323a5e1a0e6bc3324ce5260981ec55279ad31dc",
"",
"root"
],
[
"e",
"429bb79cedbf5a6447f803bfbc40b862e101f21174bee630d607b223b1301f0e",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "📅 Original date posted:2014-01-21\n📝 Original message:MultiBit here.\n\n\u003eAt least Trezor and bitcoinj (Multibit) seems to be going in this way,\n\u003ewhich is 100% of clients which expressed interest in bip39 :-).\n\u003e\n\u003eslush\n\nWe'll be using the BIP39 implementation present in Bitcoinj as slush says.\n\n\u003eProper Unicode handling is a serious issue however. You don't want\n\u003esomeone to move from one input method / machine to another and\n\u003esuddenly find that their coins are inaccessible, because of an issue\n\u003eof decomposed vs. compatibility forms or whatever.\n\nWe generate the word list internally (12,18,24) and confirm it is entered\ncorrectly through a retyping operation. This will allow us to detect\ncharacter encoding transpositions (e.g. u0032 vs u00a0) and alert the user\nbefore it becomes an issue.\n\nWhile English is the language of the first word list to be implemented, we\nwould definitely integrate alternative non-English word lists to make life\neasier for the global community. In general the approach would be for the\nuser to select their language (implying a locale) and then the word list to\nbe selected from that locale if available with a fallback to English. This\nfollows the same approach as resource bundles in Java.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140121/c576faef/attachment.html\u003e",
"sig": "8974f2cf4684cdaa1d82120f83ddc0100ad99b988bfa8d4ead276106650c41a3d8d22bcebafa72f8f79552097119b7944864cdd86400ca9dfef8d31415213a05"
}