CertiK reviewed PIVN on 13 Oct 2022: 7 findings, 0 critical; 3 marked fixed, 4 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 2 | 0 | 1 |
| Medium | 0 | 0 | 0 |
| Low | 2 | 0 | 2 |
In the contract `PIVN` the role `_owner` has authority over the following function(s): - fncLockAddress(), to lock any accounts Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and the user's assets may suffer loss.
All of the PIVN tokens are sent to the 6 EOA addresses when deploying the contract. This could be a centralization risk as the deployer can distribute PIVN tokens without obtaining the consensus of the community.
`public` functions that are never called by the contract could be declared as `external`. `external` functions are more efficient than `public` functions.
There should always be events emitted in the sensitive functions that are controlled by centralization roles.
The report names a repository or files. Open the report to see its scope.
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething 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