You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2024. It is now read-only.
With this modification the StardardToken forces the contracts receiving tokens to implement the tokenFallback method; this causes the StandardToken.sol not to follow the ERC20 standard.
I believe this method is meant to replicate the mandatory fallback on the Ethereum network, if that is the case, may be a good idea to move this to MaticWETH.sol
Another possible solution is making a nonThrow call to tokenFallback and ignore a potential failure, that will not replicate the functionality of the mandatory fallback, but it will be ERC20 compliance.
The text was updated successfully, but these errors were encountered:
But, on child chain, we want to make sure people won't lose their tokens by sending any contract which doesn't support token transfer. MaticWETH.sol will be never be deployed on mainchain.
contracts/contracts/token/StandardToken.sol
Line 22 in e59e3fb
With this modification the StardardToken forces the contracts receiving tokens to implement the tokenFallback method; this causes the StandardToken.sol not to follow the ERC20 standard.
I believe this method is meant to replicate the mandatory fallback on the Ethereum network, if that is the case, may be a good idea to move this to MaticWETH.sol
Another possible solution is making a nonThrow call to tokenFallback and ignore a potential failure, that will not replicate the functionality of the mandatory fallback, but it will be ERC20 compliance.
The text was updated successfully, but these errors were encountered: