Publish blog post regarding BIP44 derivation fix

[danfinlay]

When we move off eth-lightwallet to ethereumjs-wallet, we will be using a slightly different BIP44 derivation implementation, and we're already aware the old version has a bug that is pending merge.

This means that for something like 1 in 1000 accounts, the generated account will be different than the original account.

There are a variety of ways we can prepare for this moment.

• Axic already wrote a great blog post explaining the situation, and we should link to it when relevant.
• We could write auto-migration logic in, where we identify wrongly derived accounts, and re-create them as normal geth accounts, but this would hide from the users the fact that those accounts are no longer recoverable with their normal seed phrase (especially once we deprecate our current migration logic).
• We could provide convenient tools for recovering the old accounts.
  • Easiest way might be to simply make the latest "old style" plugin readily available for download, with instructions on installing it, and using it to move tokens to the new account.
  • We could also create an online tool for migrating assets from a deprecated account.
  • We could just brutally tell everyone it's a beta and to deal. (probably not)

[danfinlay]

I'm leaning towards 3a combined with a solid blog post linking to axic's, linking to an older build, and guiding on how to recover any assets.

Easiest way might be to simply make the latest "old style" plugin readily available for download, with instructions on installing it, and using it to move tokens to the new account.

[danfinlay]

I say this both because it is the easiest way forward for us, where we don't spend too much energy on edge cases, and also because this is a developer beta, the few affected users who need to recover anything are already early adopters, and should be capable enough of following plugin installation instructions to recover anything they've lost.

[danfinlay]

Drafting the blog post in Quip: https://consensys.quip.com/L94mADKDFiCD

[danfinlay]

Medium draft online here: https://medium.com/metamask/metamask-3-migration-guide-914b79533cdd

[danfinlay]

I think I'm going to wait until I've added a label to the recovered accounts, so I can add a screenshot to this article before publishing it, but I've updated it for all our recovery strategies, so it's pretty good to go.

[danfinlay]

Blocked by screenshots including #950

[danfinlay]

Oh we can take those screenshots now, so this is no longer blocked. Ben also wanted to know when we'd be able to publish this, so I say we groom & publish it asap.

[danfinlay]

I've updated this with the latest screenshots, ready to publish whenever we all agree to.