Question on smart contract inheriting from OpenZeppelin ERC777 implementation

Security
2

Hi @NationalPotato,

This is what I posted on the OpenZeppelin Telegram yesterday in response to a question about this:

Comparing the verified source code of the Flux token (https://etherscan.io/address/0x469eDA64aEd3A3Ad6f868c44564291aA415cB1d9#code) with a vanilla token inheriting from OpenZeppelin Contracts ERC777 implementation it appears that Flux inherits from OpenZeppelin Contracts v3.0.1 with no modification of the OpenZeppelin Contracts code.

Inheriting and extending from OpenZeppelin Contracts is how they should be used and is not plagiarism. The verified source code on Etherscan appropriately lists the license as MIT which is the opensource license used by OpenZeppelin Contracts.

As for the ERC20 approve function, it is part of the ERC20 specification and there is a well-known issue around setting allowances.
The OpenZeppelin Contracts ERC implementations should be compliant with the ERC specifications. Please report any issues on the OpenZeppelin Contracts GitHub repository.

I haven't looked at the Flux token code beyond the inheritance of the OpenZeppelin Contracts ERC777 implementation.

1 Like