Richverse Web3.

CertiK11 Apr 2022Files named in the report

Audit

CertiK reviewed Richverse (Richverse Web3.) on 11 Apr 2022: 5 findings, 0 critical; 4 marked fixed, 1 open.

No open critical findings

Open the report Open Richverse’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings5

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

Severity	Open	Fixed
Critical	0	0
High	1	1
Medium	0	0
Low	0	3

HighCentralization Related RisksFixed

In the contract `RichverseWeb3Token`, the role `owner` has authority to pause/unpause transcations over the following functions: - function pause() - function unpause() Any compromise to the `owner` account may allow a hacker to take advantage of this authority.

LowImproper Usage of `public` and `external` TypeFixed

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

LowToo Many DigitsFixed

Literals with many digits are difficult to read and review. ```solidity=10 _mint(msg.sender, 200000000000 * 10 ** decimals()); ```

LowUnlocked Compiler VersionFixed

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.