Re: [bitcoin-dev] Upgrading PoW algorithm

2018-01-20 Thread nullius via bitcoin-dev
On 2018-01-17 at 22:31:52 +, Jefferson Carpenter wrote: Bitcoin's difficulty will be maxed out within about 400 years, by Moore's law. On 2018-01-19 at 20:54:52 +, Jefferson Carpenter wrote: In other words, max difficulty for SHA256 might be significantly faster than forcing the fir

Re: [bitcoin-dev] Proposal to reduce mining power bill

2018-01-15 Thread nullius via bitcoin-dev
On 2018-01-15 at 22:47:54 +, Enrique Arizón Benito wrote: Hi all, just new to the list and curious to know if next proposal (or similar) for reducing mining-power consumption has already been discussed. The objective is to reduce the power consumption required while keeping the network

Re: [bitcoin-dev] Plausible Deniability (Re: Satoshilabs secret shared private key scheme)

2018-01-12 Thread nullius via bitcoin-dev
Preface: As a longstanding policy, whenever I buy a new hard disk or decommission an old one, I immediately `dd` it from start to end with a pseudorandom byte stream. The result is indistinguishable from my disk encryption setup, which leaves no apparent on-disk headers. I don’t do this for

[bitcoin-dev] Plausible Deniability (Re: Satoshilabs secret shared private key scheme)

2018-01-12 Thread nullius via bitcoin-dev
On 2018-01-12 at 09:50:58 +, Peter Todd wrote: On Tue, Jan 09, 2018 at 12:43:48PM +, Perry Gibson wrote: Trezor's "plausible deniability" scheme could very well result in you going to jail for lying to border security, because it's so easy for them to simply brute force alternate passw

Re: [bitcoin-dev] New Bitcoin Core macOS signing key

2018-01-12 Thread nullius via bitcoin-dev
On 2018-01-12 at 08:54:12 +, Peter Todd wrote: While a clunky way to do it, you can use the `-signer` option to tell OpenSSL to write the signer's certificate to a file. That certificate can then be compared to the one from the repo, which was still in the repo as of the (signed!) v0.15.1

Re: [bitcoin-dev] Satoshilabs secret shared private key scheme

2018-01-08 Thread nullius via bitcoin-dev
On 2018-01-08 at 04:22:43 + Gregory Maxwell wrote: I'm happy to see that there is no obvious way to abuse this one as a brainwallet scheme! BIP 39 was designed to make brainwallets secure! If a user generates a weakling 12-word mnemonic from 16 tiny octets of entropy drawn off the non-a

Re: [bitcoin-dev] BIP 39: Add language identifier strings for wordlists

2018-01-08 Thread nullius via bitcoin-dev
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"...

Re: [bitcoin-dev] BIP 39: Add language identifier strings for wordlists

2018-01-05 Thread nullius via bitcoin-dev
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.

[bitcoin-dev] BIP 39: Add language identifier strings for wordlists

2018-01-05 Thread nullius via bitcoin-dev
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

[bitcoin-dev] Bravo Charlie One: Branding Bech32

2017-12-25 Thread nullius via bitcoin-dev
I here record for the devs a thought I had a few days ago on the Bitcoin Forum about BIP 173 Bech32 addresses. I’ve heard Greg Maxwell say that “Bech32 is designed for human use and basically nothing else”; so I hope I be not untoward in considering the following human-friendliness enhancement