sign in with different wallets popup

[rymksotnini]

resolves #15

[tenthirtyone]

What's up here? Please put back to 3.4.1

[rymksotnini]

ok

[tenthirtyone]

@rymksotnini
On startup, is there additional configuration change?:

[rymksotnini]

@rymksotnini
On startup, is there additional configuration change?:

When pushing I forgot that the .env is listed in the .gitignore. So just adding the .env file in client folder will resolve the problem

[tenthirtyone]

👍 Good job

Confirming using Injected method mimics existing behavior. I was able to launch/fulfill.

@rymksotnini @mehranhydary How should we test additional login methods? I'm thinking at least the Trezor. Maybe we can task the opensource devs with testing logging in and launching a bounty?

@rymksotnini because we have the opensource devs working on issues let's make the following updates before the merge:

1. Update the README in the top-level repo with the client .env instructions.
2. Add a .env.example to the client folder with empty values for the new env vars.

After we merge I'll let the slack channel know to update their forks and merge up and give them instructions to use Injected.