POPG audit reports

Ethereumpopg.com

POPG has 1 public audit report from CertiK; dated 10 Sep 2024; no critical findings reported. It also holds 2 deployed contracts on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm12

Statuses are the security firms’ own

12 findings are still open or acknowledged in the firms’ reports: 2 high, 1 medium, 9 low (9 open, 3 acknowledged).

High
2
Medium
1
Low
9
  • High Acknowledged

    Centralization Risks in VestingWallet

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • High Acknowledged

    Initial Token Distribution

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Medium Acknowledged

    Tokens are released before the milestone starts

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Low Open

    Check-effect-interaction Pattern Violation

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Low Open

    Inconsistent token name definition

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Low Open

    Missing Zero Address Validation

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Low Open

    Potentially misconfiguration in the constructor

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Low Open

    Redundant Inheritances

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Low Open

    Redundant to recalculate the `currentPhase`

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

  • Low Open

    The `benificiary` of `InforDistribute` is not upd

    POPG Token - Audit · CertiK · 10 Sep 2024 · Report ↗

All 12 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
POPG Token - AuditSecurity firm: CertiKDate: Scope: 2 addresses on EthereumNone openFindings: 2 high · 1 medium · 9 low
3 acknowledged · 9 open
skynet.certik.com ↗

Findings12

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

SeverityOpenAcknowledgedFixed
Critical000
High020
Medium010
Low900
LowCheck-effect-interaction Pattern ViolationPOPG Token - Audit · CertiK · 10 Sep 2024Open

In the `release()` function, the variables `_erc20Released[token]` and `milestones` are updated after the `distributeRecipient()` and perform an external calls `IERC20(token).transfer`, which violates the check-effect-interaction pattern.

Open the report
LowInconsistent token name definitionPOPG Token - Audit · CertiK · 10 Sep 2024Open

The token contract has inconsistent token name definitions in its constructor. The token name defined for the ERC20 contract is "POPG", while the token name defined for the EIP 712 domain separator (used in ERC20Permit) is "POPG Token": ```solidity=12 constructor(address _vestingWallet) ERC20("POPG", "POPG") ERC20Permit("POPG Token") ``` According to the [ERC20Permit](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/c1d6ad5a307945c7825cb3c4c911f2fd017c8725/contracts/token/ERC20/extensions/ERC20Permit.sol#L37) comment: "It's a good idea to use the same `name` that is defined as the ERC20 token name.". This implies that the token name used to initiate the `ERC20` potentially incorrect.

Open the report
LowMissing Zero Address ValidationPOPG Token - Audit · CertiK · 10 Sep 2024Open

Addresses are not validated before assignment or external calls, potentially allowing the use of zero addresses and leading to unexpected behavior or vulnerabilities. For example, transferring tokens to a zero address can result in a permanent loss of those tokens. ```solidity=51 businessMarketing = _defaultBenificiary; ``` ```solidity=52 presale = _defaultBenificiary; ``` ```solidity=53 reserve = _defaultBenificiary; ``` ```solidity=54 advisor = _defaultBenificiary; ``` - `_defaultBenificiary` is not zero-checked before being used.

Open the report
LowPotentially misconfiguration in the constructorPOPG Token - Audit · CertiK · 10 Sep 2024Open

There is a misconfiguration in the `inforDistributes` mapping, which associates distribution percentages with recipient indices that correspond to the `_recipients` array: ```solidity=56 _recipients = [businessMarketing, presale, reserve, advisor]; ``` The `inforDistributes` mapping is structured to hold an array of `InforDistribute` structs, keyed by the recipient index: `recipient_index => [{beneficiary, percentage, phase}, ...]`. ```solidity=40 mapping(uint8 => InforDistribute[]) internal inforDistributes; ``` - The `recipient_index` is the array index of the `_recipients` array. - The `beneficiary` address is the token recipient. A discrepancy has been found where entries intended for the `presale` account are mistakenly assigned to the `reserve` account, for example: ```solidity=71 inforDistributes[2].push(InforDistribute(presale, 55, 2)); ``` Here, the `recipient_index` is set to `2`, which, according to the `_recipients` array, corresponds to the `reserve`, not the `presale`. However, the `beneficiary` is set to the `presale` address. Although all recipients are defaulted to the same address in the constructor, the inconsistency in the code logic would lead to confusion.

Open the report
LowRedundant InheritancesPOPG Token - Audit · CertiK · 10 Sep 2024Open

The `POPGToken` contract inherits from `ERC20`, `ERC20Permit` and `Ownable`, but the ownership functionality appears unused. This redundancy can cause confusion and might be optimized for efficiency: ```solidity=9 contract POPGToken is ERC20, ERC20Permit, Ownable { ```

Open the report
LowRedundant to recalculate the `currentPhase`POPG Token - Audit · CertiK · 10 Sep 2024Open

In the `release()` function, the `currentPhase` is calculated and cached in L263: ```solidity=263 uint256 currentPhase = getPhaseAtTime(block.timestamp); ``` However, it is recalculated again in the function: ```solidity=276 milestones[getPhaseAtTime(block.timestamp)].released = true; ``` Recalculating the `currentPhase` is redundant since it has already been determined and stored earlier in the function.

Open the report
LowThe `benificiary` of `InforDistribute` is not updPOPG Token - Audit · CertiK · 10 Sep 2024Open

The `changeAddressBeneficiary()` function intends to update the beneficiary address within the `InforDistribute` struct for a given recipient index. However, the function only updates the beneficiary address of the first entry in the `InforDistribute` array associated with the provided index: ```solidity=146 inforDistributes[_index][0].benificiary = _benificiary; ``` When this function is called with an index and a new beneficiary address, it does not iterate through the entire array of `InforDistribute` structs at that index. As a result, only the first entry is updated, which can lead to inconsistencies where subsequent entries retain the old beneficiary address. For example, calling `changeAddressBeneficiary(3, newAdvisor)` only updates the beneficiary for the first entry at index 3, while other entries such as `inforDistributes[3][1]` and `inforDistributes[3][2]` remain unchanged.

Open the report
LowThe `InforDistribute` saves inaccurate phasesPOPG Token - Audit · CertiK · 10 Sep 2024Open

The index of `milestones` array should match with the phrase number based on the logic in the `getTotalDistributedAmount()`, `release()` and `unlockRestAmount()` functions. The contract contains a mismatch between the index of the `milestones` array and the associated phrase number. The `milestones` array uses zero-based indexing, where the first milestone is at index 0: ```solidity milestones[0] = Milestone(MILESTONE_1_DATE, 20, false); ``` However, the first phrase number in the `InforDistribute` struct is initialized with a value of 1, as shown below: ```solidity inforDistributes[0].push(InforDistribute(businessMarketing, 35, 1)); ``` This discrepancy could lead to inconsistencies and confusion.

Open the report
LowUnused `SafeERC20` LibraryPOPG Token - Audit · CertiK · 10 Sep 2024Open

The `VestingWallet` contract imports and declares usage of the `SafeERC20` library for the `IERC20` interface: ```solidity=11 using SafeERC20 for IERC20; ``` However, throughout the contract, the `SafeERC20` library functions are not utilized when transferring tokens. This can lead to missed safety checks during token transfers, such as checking for a successful transfer, which `SafeERC20` provides.

Open the report

Contracts2

AddressChainSource code
0x59caf3854a29d886080fe28dfecb2dec61cf5ba2Chain: EthereumSource code: Verified source
0xdac070102b0cfde1493026454c9c608924f6db71Chain: EthereumSource code: Verified source

POPG: questions

Is POPG audited?

Trustblock holds 1 public audit report for POPG, dated 10 Sep 2024. The latest is by CertiK (“POPG Token - Audit”).

Who audited POPG?

CertiK wrote the report Trustblock holds for POPG.

Are there open findings in POPG’s audits?

12 findings are still open or acknowledged in the firms’ reports: 2 high, 1 medium, 9 low (9 open, 3 acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="popg"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

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