Refactor: Removes HathorWallet from Redux store

[tuliomir]

The next version of Redux throws an error by default whenever there are non-serializable objects in its Store ( more about this on this article ). This PR is one in a series of PRs that aim to refactor all of those instances before the upgrade.

The wallet Redux property stored is currently used for many operations throughout the whole application. The proposed solution is to:

• Create a wallet singleton javascript module, apart from the Redux store
• Refactor all the calls from this store property to use the singleton directly

It is worth noting that we plan on implementing multiple simultaneous wallets in the future ( see #210 ). This refactor also aims to facilitate this feature, while not directly implementing it.

Acceptance Criteria

• The routerHistory should not be present on the Redux Store

Rationale and Alternatives

Many different approaches were considered for this refactor, the most important ones were using useRef and useContext. The idea is to keep this wallet instance in a way that does not cause:

• Additional cognitive overhead due to abstractions
• Bugs with future iterations of React
• Compatibility with the React conventions

Since useContext is meant to deal with serializable data that will affect rendering, it was not an option for this solution. Creating a new component and applying useRef would be a possibility, but this would not offer any benefit over a common javascript singleton.

So, the decided solution was to implement a singleton for the application HathorWallet instance.

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[r4mmer]

As stated in the review, I think we should remove the wallet from all mapStateToProps since the objective of this PR is to remove the wallet from redux state.