Ethereum Stack Exchange is a question and answer site for users of Ethereum, the decentralized application platform and smart contract enabled blockchain. It only takes a minute to sign up.
Sign up to join this community
On the one hand, protecting from over- and underflow is a must, and a widely used SafeMath library can help with that. SafeMath throws in case of error.
On the other hand, ERC20 token functions are expected to return false on failure, not throw. This presentation advises against throwing in transfer and other ERC20 functions that return bool(success).
What is the proper way of protecting against integer errors in tokens while conforming to the API?
There's actually an issue in SafeMath's repo that has been there for a while which references this subject. https://github.com/OpenZeppelin/zeppelin-solidity/issues/435
There's also a PR submitted but not yet merged. https://github.com/OpenZeppelin/zeppelin-solidity/pull/468
I guess you could replace SafeMath for this code if you really need to make the token 100% compliant, or wait a while until they do merge that PR.
