In the contract `Blockearth` the role `_owner` has authority over the following functions:  
- renounceOwnership(): leaves the contract without owner
- transferOwnership(): transfers ownership of the contract to a new account
- withdraw(): claims any ERC20 tokens in contract to the owner account
- withdrawBNB(): claims BNB in contract to the owner account

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

Centralization Risks in Blockearth.sol

All of the `BLET` tokens(1 billion) are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute `BLET` tokens without obtaining the consensus of the community.

Initial Token Distribution

The `Blockearth` contract lacks the payable function and cannot accept BNB, so `withdrawBNB` function is meaningless.

Contract Lacks Payable Function

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

Missing Emit Events

The contract has unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to differing compiler version numbers. This can lead to an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

Blockearth

Highlights & Alerts

This is just a placeholder

highlight placeholder lorem Ipsum...

highlight lorem

This is a alert demo

Alert demo

Code Audit History

5

0

5

0

0