Interaction with deployed contracts in frontend isn't stable #5
Description
At the time of first development, the library for interacting with an Ethereum blockchain via JS was in a shifting state between dev and stable (see https://github.com/ethereum/web3.js/). This resulted in a lot of uncertainty when developing, as documentation wasn't up to speed with the available libraries.
Right now all the interactions between the application frontend and the deployed Qoop contract is hacked together, and needs to be reviewed from the ground up. This includes interaction with the user's wallet, which is being done via the Metamask browser extension, but ideally should allow for access using the user's private key as well.
I would suggest tackling this by looking at the current version of Web3, which should have changed in the meanwhile, and compare it's API to our current implementation to see what critical paths have changed.