Removes the DomainAware contract from ERC20Token and ERC721Token
Motivation and Context
Currently, the DomainAware uses the chainId opcode to determine what chain the current Contract is running on. However, some internal tools do not support this opcode (yet), and since these tokens aren't ever doing any signing verification (unlike ERC1400Token) it is safe to remove for now to get internal tools working.
Once internal tools have been updated to support the chainId opcode, this should be added back to these contracts
How Has This Been Tested?
All unit tests are passing, currently nothing was using the DomainAware contract for ERC20Token and ERC721Token
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
Removes the
DomainAware
contract fromERC20Token
andERC721Token
Motivation and Context
Currently, the
DomainAware
uses thechainId
opcode to determine what chain the current Contract is running on. However, some internal tools do not support this opcode (yet), and since these tokens aren't ever doing any signing verification (unlikeERC1400Token
) it is safe to remove for now to get internal tools working.Once internal tools have been updated to support the
chainId
opcode, this should be added back to these contractsHow Has This Been Tested?
All unit tests are passing, currently nothing was using the
DomainAware
contract forERC20Token
andERC721Token
Types of changes
Checklist: