That's the point indeed and the scope is wider than XYZIP-39, even if
what I mean is the very contrary of your point (really bitcoin is
reserved to an elite understanding english/ascii letters?)
This proposal is tailor made for Trezor and does not simplify anything
for people, that's the contrary
>I'm shocked that so many people are resisting the idea that just *maybe* there
could be people in other parts of the world who do not want to use or
cannot use the strict set of latin characters and words from the English
language.
You're mistaking concern for users potentially losing money with
Greg yes, there were already examples in this very thread of people
explaining how they use languages other than English. I'm shocked that so
many people are resisting the idea that just *maybe* there could be people
in other parts of the world who do not want to use or cannot use the strict
set of
> Let me re-phrase: Is it a known thing for users to actually use it?
yes. Based on language stats from the app stores, roughly 30% to 40% of
Copay users have their backup on a language
other than English, and we constantly get requests to support new languages
in BIP39.
On Mon, Jan 8, 2018 at 11
On Mon, Jan 8, 2018 at 11:34 AM, Greg Sanders via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Has anyone actually used the multilingual support in bip39?
>
Copay (and all its clones) use it.
>
> If a feature of the standard has not been(widely?) used in years, and
> isn't
Let me re-phrase: Is it a known thing for users to actually use it?
On Mon, Jan 8, 2018 at 9:52 AM, Matias Alejo Garcia
wrote:
>
>
> On Mon, Jan 8, 2018 at 11:34 AM, Greg Sanders via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Has anyone actually used the multilingual supp
Has anyone actually used the multilingual support in bip39?
If a feature of the standard has not been(widely?) used in years, and isn't
supported in any major wallet(?), it seems indicative it was a mistake to
add it in the first place, since it's a footgun in the making for some poor
sap who can'
On 2018-01-08 at 07:35:52 +, 木ノ下じょな
wrote:
This is very sad.
The number one problem in Japan with BIP39 seeds is with English words.
I have seen a 60 year old Japanese man writing down his phrase (because
he kept on failing recovery), and watched him write down "aneter" for
"amateur"...
This is very sad.
The number one problem in Japan with BIP39 seeds is with English words.
I have seen a 60 year old Japanese man writing down his phrase (because he
kept on failing recovery), and watched him write down "aneter" for
"amateur"...
So instead I had him use Copay which generates Japan
Calm down now and stop your "do you want a" or "link" stupid comments,
whether you are really willing to propose some improvements, whether you
are just posting for nothing
BIP39:
"The length of the derived key is 512 bits (= 64 bytes).
This seed can be later used to generate deterministic walle
Unfortunately, even "yourself" seems not to know what he is talking
about (so imagine for other people, 256 bits is advised --> 32B),
probably that's why you brought this discussion off the list, then
making recommendations to improve something that is misleading and messy
is quite dubious
And may
On 05/01/18 14:58, nullius via bitcoin-dev wrote:
> I propose and request as an enhancement that the BIP 39 wordlist set
> should specify canonical native language strings to identify each
> wordlist, as well as short ASCII language codes. At present, the
> languages are identified only by their n
No that's not, some parts of the answer might be but this related, this
just shows how people use wrongly BIP39 and subsequent BIPs (and
globally other things), misleading them, while the advantage of using it
is quite dubious compared to backing up a seed, unless you can convince
me of the contrar
On 2018-01-05 at 16:04:10 +, Sjors Provoost
wrote:
I’m not a fan of language specific word lists within the current BIP-39
standard. Very few wallets support anything other than English, which
can lead to vendor lock-in and long term loss of funds if a rare
non-English wallet disappears.
See: https://github.com/Ayms/bitcoin-transactions/issues/3
OK, maybe it's my fault, I did not foresee this case, and now it's
working for p2sh (non segwit)
From my standpoint this just means that BIP39/44 stuff should be
eradicated (not BIP141 but see what happened...), this is of no use,
confusi
I don’t know about Electrum but many wallets validate the English words, which
helps in catching typos.
Hardware wallets without a full keyboard, like the Ledger Nano S, won’t even
let you freely type characters; you have to select words from a list.
So although the standard technically allows
I’m not a fan of language specific word lists within the current BIP-39
standard. Very few wallets support anything other than English, which can lead
to vendor lock-in and long term loss of funds if a rare non-English wallet
disappears.
However, because people can memorize things better in the
I propose and request as an enhancement that the BIP 39 wordlist set
should specify canonical native language strings to identify each
wordlist, as well as short ASCII language codes. At present, the
languages are identified only by their names in English.
Strings properly vetted and recommen
18 matches
Mail list logo
