Vim - Audit

CertiKFiles named in the report

CertiK reviewed VIM (Vim - Audit) on 10 Aug 2023: 8 findings, 1 critical; 3 marked fixed, 5 acknowledged.

1 critical finding, fixed
Open the reportOpen VIM’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings8

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical001
High042
Medium000
Low010
HighCentralization Related Risks in `VIUToken`Acknowledged

In the contract `Ownable`, the role `_owner` has authority over the following functions: - renounceOwnership() - transferOwnership() Any compromise to the `_owner` account may allow a hacker to take advantage of this authority and renounce or transfer the ownership. --- In the contract `VIUToken`, the role `_owner` has authority over the following functions: - mint() - mintTo() Any compromise to the `_owner` account may allow a hacker to take advantage of this authority and mint tokens. --- Important Note: Certain identification and KYC procedures were attempted to be applied to the project team in order to better understand the centralization situation and potential risks of the project. Based on the collected information and further conducted investigation, the project passed the criteria with a certain amount of requirements satisfied for the investigation. Still we strongly advise end users to conduct further research and exercise due diligence before engaging with the project. It is crucial for end users to independently verify and assess all available information to make informed decisions.

HighInitial Token Distribution in `VIUToken`Acknowledged

A large number of VIU tokens are sent to the contract deployer when deploying the `VIUToken` contract. This could be a centralization risk as the anonymous deployers can distribute tokens without obtaining the consensus of the community. Any compromise to the deployer accounts that holds undistributed tokens may allow the attacker to steal and sell tokens on the market, resulting in severe damage to the project. --- Important Note: Certain identification and KYC procedures were attempted to be applied to the project team in order to better understand the centralization situation and potential risks of the project. Based on the collected information and further conducted investigation, the project passed the criteria with a certain amount of requirements satisfied for the investigation. Still we strongly advise end users to conduct further research and exercise due diligence before engaging with the project. It is crucial for end users to independently verify and assess all available information to make informed decisions.

HighInitial Token Distribution in `VIZToken`Acknowledged

A large number of VIZ tokens are sent to the contract deployer when deploying the `VIZToken` contract. This could be a centralization risk as the anonymous deployers can distribute tokens without obtaining the consensus of the community. Any compromise to the deployer accounts that holds undistributed tokens may allow the attacker to steal and sell tokens on the market, resulting in severe damage to the project. --- Important Note: Certain identification and KYC procedures were attempted to be applied to the project team in order to better understand the centralization situation and potential risks of the project. Based on the collected information and further conducted investigation, the project passed the criteria with a certain amount of requirements satisfied for the investigation. Still we strongly advise end users to conduct further research and exercise due diligence before engaging with the project. It is crucial for end users to independently verify and assess all available information to make informed decisions.

HighMinting Centralization Risks in `VIUToken`Acknowledged

In the contracts `VIUToken`, the role `_owner` has the authority to mint an arbitrary amount of tokens to an arbitrary address. Any compromise to the `_owner` account may allow a hacker to take advantage of this authority and mint a huge amount of tokens to themselves. The hacker could sell those tokens and cause the token price to drop. --- Important Note: Certain identification and KYC procedures were attempted to be applied to the project team in order to better understand the centralization situation and potential risks of the project. Based on the collected information and further conducted investigation, the project passed the criteria with a certain amount of requirements satisfied for the investigation. Still we strongly advise end users to conduct further research and exercise due diligence before engaging with the project. It is crucial for end users to independently verify and assess all available information to make informed decisions.

LowWeak PRNGAcknowledged

Weak PRNG due to a modulo on `block.timestamp`, `block.difficulty`, `msg.sender`, `block.coinbase`, `block.number`, `gasLeft` or `blockhash`. These can be influenced by miners to some extent, so they should be avoided. ```solidity=14 uint256 randomNumber = uint256(keccak256(abi.encodePacked(block.number, nonce, msg.sender, block.timestamp, block.difficulty))) % (_max - _min+1); ```

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (3)

  • contracts/VIZToken.sol
  • contracts/VIUToken.sol
  • contracts/RandomGenerator.sol

Part of VIM’s security record

VIM
Audits1 audit by 1 firmLast audit Aug 2023, by CertiK.
Critical findingsNo open critical findingsIn that report, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open VIM’s security record

Security firm

CertiK

1,044 projects reviewed · 1,375 reports · latest May 2025

See CertiK’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us