Part of CertiK’s retainer series
CertiK reviewed WEMIX (Wemix 99 PlayNFTMarket) on 1 Mar 2024: 5 findings, 0 critical; 2 marked fixed, 3 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 | 0 |
| Medium | 0 | 0 | 1 |
| Low | 1 | 0 | 1 |
The contract exhibits an inconsistency in its support for native tokens as a form of payment. The function `addNFTPayment()` is designed to add supported payment tokens, but it explicitly disallows the native token by requiring the payment token address not to be zero: ```solidity=243 // addNFTPayment() require(payments[i] != address(0), "MB : payment is zero"); ``` ```solidity=262 // removeNFTPayment() require(collection != address(0) && payment != address(0), "MB: zero address request"); ``` On the other hand, the market contract's `registerBuyOrder()` function suggests that native tokens are intended to be supported as it checks for an address of zero (indicative of native tokens) and processes the payment accordingly: ```solidity=97 // PlayMarketBaseV4::registerBuyOrder() if(_order.payment == address(0)){ require(msg.value == orderPrice, "MB: invalid value"); (result, order) = IOrder(payable(strategy)).open{value:msg.value}(_order); } else { ``` This discrepancy indicates that while the market contract is set up to handle native tokens, the `addNFTPayment()` function prevents their use, which could be a design flaw or oversight.
The upgradable contract `PlayMarketTokenManagerV3` imports the non-upgradable contract `Ownable`, which is not utilized within the contract.
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