P2SH^2 wasn't a serious proposal-- I just suggested it as a thought
experiment. I don't think it offers much useful in the context of
Bitcoin today. Particularly since weight calculations have made output
space relatively more expensive and fees are at quite non-negligible
rates interest in
I've posted an initial draft of a possible Bech32 revision/replacement here:
https://github.com/luke-jr/bips/blob/new_bech32_p2sh2/bip-bech32-p2sh2.mediawiki
On Thursday 04 January 2018 2:23:05 PM Luke Dashjr via bitcoin-dev wrote:
> I know I'm super-late to bring this up, but was there a reason
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
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
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,
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
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