[bitcoin-dev] bip39

2022-01-17 Thread Erik Aronesty via bitcoin-dev
really don't like that art, work, and artwork are 3 different words would be nice to clean up adjacent ambiguity it's not a big deal, but it can lead to confusion when writing things down dup: ('canal', 'arm') ('can', 'alarm') dup: ('canal', 'one') ('can', 'alone') dup: ('canal', 'ready')

Re: [bitcoin-dev] bip39

2022-01-17 Thread Jeremy via bitcoin-dev
This is a good point, but can be addressed by having a non-void whitespace character (e.g., win x estate). changing BIP39 would be hard since software expects a standard list; it would also be possible to rejection sample for seeds that do not contain these pairs, unclear how much entropy would

Re: [bitcoin-dev] bip39

2022-01-17 Thread Pavol Rusnak via bitcoin-dev
Trezor recovery cards look like this what addresses the issue: https://wiki.trezor.io/images/Seed_card_example.jpg 1. Each word has a box around it. 2. You write the words one under the other, not next to each other. On Mon, 17 Jan 2022 at 23:38, Jeremy via bitcoin-dev <

[bitcoin-dev] SASE Invoices

2022-01-17 Thread Jeremy via bitcoin-dev
Devs, I was recently speaking with Casey R about some of the infrastructural problems with addresses and felt it would be worth summarizing some notes from that conversation for y'all to consider more broadly. Currently, when you generate (e.g., a Taproot address): - The key may or may not be a