Consider creating a bridge + MEW bundle for offline use

[x1ddos]

This came up while discussing #7.

Currently, users need to run a separate static file server like python3 -m http.server --bind 127.0.0.1 and open http://localhost:port to access MEW offline. Opening an HTML file directly with a browser is suboptimal. For example, see security considerations and corner cases.

It feels like a bundle of MEW + the bridge including a built-in static file server would be very helpful for those who want to use BitBox02 with MEW offline.

Such a bundle would nicely package everything together: the bridge, MEW release and a static server. It would be an alternative package, released alongside the regular bridge.

[benma]

I don't know if something changed on MEW's side, but if I clone their repo and do

npm i
npm run dev

I get a fully functioning MEW that works with the BitBox02, locally.

[x1ddos]

The idea here was to create a complete offline bundle but npm i would need internet connection.

[benma]

Does MEW even do anything when offline? It also needs to fetch balances etc. somehow. Or maybe it can be used to just sign offline, that would be nice.

[x1ddos]

Yeah, that's exactly what it seems to say on https://kb.myetherwallet.com/en/offline/using-mew-offline/

The main computer being used to generate the transactions should not be connected to the internet. You can generate a wallet completely offline and send transactions on a different computer, which must be connected to the internet, from our ‘Send Offline’ section.