TokenSoft Token

Smart contracts will often have `Owner` variables to designate the person with special privileges to make modifications to the smart contract. Currently, the `Owner` role can add/remove other roles as well as other owners. Moreover, the `Revoker` role can transfer funds between users readily, which may be a dangerous privilege. If these privileged members lose their private keys, regular users may suffer from lost funds and unexpected behaviour.

As it presently is constructed, the contract is vulnerable to the [allowance double-spend exploit](https://github.com/OpenZeppelin/openzeppelin-solidity/blob/b4f87bb8fc25fb07f73099701e39e167a3d36465/contracts/token/ERC20/ERC20.sol#L71-L78), as with other ERC20 tokens.

In the constructor of `Proxy.sol`there is no verification as to whether or not `contractLogic` contains code. This creates a risk for human errors were during the `Proxy` contract deployment where an arbitrary externally owned account may be stored instead of a contract account inside the proxy. Furthermore, executing transactions on a non-contract address will not throw any errors, which can be problematic.