In the contract `CAIZCOIN` 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 and control the ICO status, change rate, and mint tokens.

![](https://accelerator-tasks-prod.s3.amazonaws.com/fd6ba9c1b570472c929b3d00c4d5f01c/diagrams/centralization-CAIZCOIN-_owner.svg)

In the contract `Owned` 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 and transfer the ownership.

![](https://accelerator-tasks-prod.s3.amazonaws.com/fd6ba9c1b570472c929b3d00c4d5f01c/diagrams/centralization-Owned-_owner.svg)


Centralization Risk in caizcoin.sol

CAIZ only receives ETH and returns the swapped CAIZ Token. As a token exchange contract, some careless users would transfer other tokens which are not supported like USDC or USDT to it by mistake. In this case, the transferred USDT or USDC would be locked in the contract address, because there is no rescue method for the unexpected token transfer.

Users should beware only ETH and CAIZ token could be withdrawn from this contract.

Recieved Unsupported Token Will Be Locked

The total supply had declared as 99,999,999 CAIZ in the comments and CAIZ's whitepaper.
```solidity=8
// 'CAIZCOIN' Smart Contract
//
// OwnerAddress : 0xfd413f4BC3A72907Bc829Da1622F087b4E5B038d
// Symbol       : CAIZ
// Name         : CAIZCOIN
// Total Supply : 99,999,999 CAIZ
// Decimals     : 18
```
And the total supply of tokens had already been distributed to the owner in the constructor.
```solidity=123
    balances[owner] = _totalSupply;
```
But the `mint` function privileged by the owner could mint more tokens to an address, which would cause an increase in the liquidity of CAIZ in the markets.

Additional Token Is Mintable Beyond The Anounced TotalSupply

There should always be events emitted in the sensitive functions that are controlled by centralization roles:
- stopICO
- resumeICO

Missing Emit Events

`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 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 different compiler versions. 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.

Unlocked Compiler Version

The **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.

Missing Error Messages

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

Caizcoin

Highlights & Alerts

This is just a placeholder

highlight placeholder lorem Ipsum...

highlight lorem

This is a alert demo

Alert demo

Code Audit History

8

0

8

0

0