Part of CertiK’s retainer series
CertiK reviewed WEMIX (Wemix WemixDollarPaymentV2 - Retainer#17) on 16 Mar 2023: 8 findings, 0 critical; 4 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 | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 4 | 0 | 4 |
The implementation of the `isContract` check can not cover all scenarios. The check can be bypassed if the call is from the constructor of a smart contract or when the contract is destroyed. In that case, the codesize will also be zero. The "isContract" function in the OpenZeppelin "Address" library uses the same implementation, but comments mention that "it's unsafe to rely on the check and it can be bypassed". Reference: https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/Address.sol
There should always be events emitted in the sensitive functions that are controlled by centralization roles.
The contract is serving as the underlying entity to interact with one or more protocols via interfaces. The scope of the audit treats third party entities as black boxes and assume their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=47 IPlaySwapRouter _router; ``` - The contract `WemixDollarPaymentV2` interacts with third party contract with `IPlaySwapRouter` interface via `_router`. --- ```solidity=53 address private _dollar; ``` - The contract `WemixDollarPaymentV2` interacts with third party contract with `IERC20` interface via `_dollar`. --- ```solidity=54 address private _recipient; ``` - The contract `WemixDollarPaymentV2` interacts with third party contract with `IRecipientRoleV6` interface via `_recipient`.
Solidity frequently releases new compiler versions. Using an old version prevents access to new Solidity security features. We also recommend avoiding complex `pragma` statements. ```x Pragma version^0.6.0 (contracts/Common/UserNonce.sol#3) allows old versions ``` ```solidity=3 pragma solidity ^0.6.0; ``` --- ```x Pragma version^0.6.0 (contracts/Role/IRecipientRoleV6.sol#3) allows old versions ``` ```solidity=3 pragma solidity ^0.6.0; ``` --- ```x Pragma version<=0.7.0 (contracts/openzeppelin-solidity/contracts/GSN/Context.sol#3) uses lesser than ``` ```solidity=3 pragma solidity <=0.7.0; ``` --- ```x Pragma version<=0.7.0 (contracts/openzeppelin-solidity/contracts/cryptography/ECDSA.sol#3) uses lesser than ``` ```solidity=3 pragma solidity <=0.7.0; ``` --- ```x Pragma version^0.6.3 (contracts/openzeppelin-solidity/contracts/drafts/Counters.sol#3) allows old versions ``` ```solidity=3 pragma solidity ^0.6.3; ``` --- ```x Pragma version<=0.7.0 (contracts/openzeppelin-solidity/contracts/ownership/Ownable.sol#3) uses lesser than ``` ```solidity=3 pragma solidity <=0.7.0; ``` --- ```x Pragma version^0.6.3 (contracts/openzeppelin-solidity/contracts/ownership/Secondary.sol#3) allows old versions ``` ```solidity=3 pragma solidity ^0.6.3; ``` --- ```x Pragma version^0.6.3 (contracts/openzeppelin-solidity/contracts/utils/Address.sol#3) allows old versions ``` ```solidity=3 pragma solidity ^0.6.3; ```
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (1)
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