MetaMask: Use web3.currentProvider instead of window.web3

[vitvly]

Summary

When browsing Open Bounty website with MetaMask on, it complains in Console that

MetaMask: web3 will be deprecated in the near future in favor of the ethereumProvider 
https://github.com/MetaMask/faq/blob/master/detecting_metamask.md#web3-deprecation

Solution

Following the above given document, use web3.currentProvider instead of window.web3 when calling MetaMask in application code.

[status-open-bounty]

Current balance: 0.0 ETH Tokens: SNT: 240.00 Contract address: 0x78fb1c9c203d1f3d0ea421a7bdaf61ae6d9b5a52 Network: Mainnet To claim this bounty sign up at https://openbounty.status.im and make sure to update your Ethereum address in My Payment Details so that the bounty is correctly allocated. To fund it, send ETH or ERC20/ERC223 tokens to the contract address.

[martinklepsch]

This should be super easy to fix by upgrading cljs-web3 to 0.19.0-0-11 and replacing the web3 constructor we defined here: https://github.com/status-im/open-bounty/blob/b76ad70766e7d521f2df0c0ee3d7d59d533fd399/src/cljs/commiteth/common.cljs#L10-L11

with the one that has been added to cljs-web3 in this PR: https://github.com/district0x/cljs-web3/pull/8

[debragail]

do we need to fix this anywhere else?

[debragail]

I think this was fixed?

[pablanopete]

To be revoked @andytudhope