In the contract `EggNFT` the role `LAUNCHPAD` has authority over the functions shown in the diagram below.

Any compromise to the `LAUNCHPAD` account may allow the hacker to take advantage of this authority.

![](https://accelerator-tasks-prod.s3.amazonaws.com/791e2c0b83024f0aaef543ed0f60b9e9/diagrams/centralization_EggNFT-EggNFT-LAUNCHPAD.svg)

---

In the contract `EggNFT`, the role `onlyMint` has authority over the following functions:
- createNFT()

---

In the contract `EggNFT` the role `_owner` has authority over the functions shown in the diagram below.

Any compromise to the `_owner` account may allow the hacker to take advantage of this authority.

![](https://accelerator-tasks-prod.s3.amazonaws.com/791e2c0b83024f0aaef543ed0f60b9e9/diagrams/centralization_EggNFT-EggNFT-_owner.svg)

Centralization Risks in EggNFT.sol

There should always be events emitted in the sensitive functions that are controlled by centralization roles.

Missing Emit Events

Addresses should be checked before assignment or external call to make sure they are not zero addresses.

```solidity=126
        LAUNCHPAD = _launchpad;
```
- `_launchpad` is not zero-checked before being used.



Missing Zero Address Validation

`public` functions that are never called by the contract could be declared as `external`. `external` functions are more efficient than `public` functions.

Improper Usage of `public` and `external` Type

The linked variables could be declared as `constant` since these state variables are never modified.

Variables That Could Be Declared as `constant`

The `totalSupply()' function is not required in `4.x' of the openzeppelin library. ([Reference Docs](https://docs.openzeppelin.com/contracts/4.x/api/token/erc721#IERC721))

Monster GO

Highlights & Alerts

This is just a placeholder

highlight placeholder lorem Ipsum...

highlight lorem

This is a alert demo

Alert demo

Code Audit History

6

0

3

0

3