Metathings has 1 public audit report from CertiK; dated 27 Jan 2023; no critical findings reported. It also holds 1 deployed contract on 1 chain.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
12 findings are still open or acknowledged in the firms’ reports: 3 high, 9 low (9 open, 3 acknowledged).
Centralization Risks in AntiBotLiquidityGenerator
METT · CertiK · 27 Jan 2023 · Report ↗
Contract Gains Non-Withdrawable BNB Via The `swap
METT · CertiK · 27 Jan 2023 · Report ↗
Initial Token Distribution
METT · CertiK · 27 Jan 2023 · Report ↗
Incorrect error message
METT · CertiK · 27 Jan 2023 · Report ↗
Missing Emit Events
METT · CertiK · 27 Jan 2023 · Report ↗
Missing Zero Address Validation
METT · CertiK · 27 Jan 2023 · Report ↗
Potential Logic Flaw in Reward Calculation
METT · CertiK · 27 Jan 2023 · Report ↗
Redundant code
METT · CertiK · 27 Jan 2023 · Report ↗
The purpose of function `deliver`
METT · CertiK · 27 Jan 2023 · Report ↗
Unknown Implementation of `onPreTransferCheck`
METT · CertiK · 27 Jan 2023 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| METT | Security firm: CertiK | Date: | Scope: 1 address on BNB Chain | None open | Findings: 3 high · 9 low 3 acknowledged · 9 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 3 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 9 | 0 | 0 |
The error message in `require(_isExcluded[account], "Account is already excluded")` does not describe the error correctly.
Open the reportThere should always be events emitted in the sensitive functions that are controlled by centralization roles.
Open the reportAddresses should be checked before assignment or external call to make sure they are not zero addresses. ```solidity=1065 payable(serviceFeeReceiver_).transfer(serviceFee_); ``` - `serviceFeeReceiver_` is not zero-checked before being used.
Open the reportTo the best of understanding, the reward of a specific account should stop accumulating while in the range of being excluded from reward after calling `excludeFromReward()`. In L1218, the current `_tOwned` balance of the `account` is recorded and any reward starting from this point should not be accumulated after calling the function `excludeFromReward()`. However, when calling the function `includeInReward()` to include the excluded `account` for reward, `_rOwned` should be calculated with current `_tOwned` value.
Open the reportThe condition `!_isExcluded[sender] && !_isExcluded[recipient]` can be included in `else` .
Open the reportThe function `deliver()` can be called by anyone. It accepts an uint256 number parameter `tAmount`. The function reduces the METT token balance of the caller by `rAmount`, which is `tAmount` reduces the transaction fee. Then, the function adds `tAmount` to variable `_tFeeTotal`, which represents the contract's total transaction fee. We wish the team could explain more on the purpose of having such functionality.
Open the reportThe method `onPreTransferCheck` in `pinkAntiBot` is unknown implementation. ```solidity=1493 if (enableAntiBot) { pinkAntiBot.onPreTransferCheck(from, to, amount); } ``` The scope of the audit treats 3rd party entities as black boxes and assumes their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts, such as increasing fees of 3rd parties, migrating to new LP pools, etc.
Open the reportThe return value of an external call is not stored in a local or state variable. ```solidity=1574 uniswapV2Router.addLiquidityETH{value: ethAmount}( address(this), tokenAmount, 0, // slippage is unavoidable 0, // slippage is unavoidable address(0xdead), block.timestamp ); ```
Open the reportThe linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x7082…a8100x7082ff3a22e707136c80a9efcb215ec4c1fda810 | Chain: BNB Chain | Source code: Verified source |
Trustblock holds 1 public audit report for Metathings, dated 27 Jan 2023. The latest is by CertiK (“METT”).
CertiK wrote the report Trustblock holds for Metathings.
12 findings are still open or acknowledged in the firms’ reports: 3 high, 9 low (9 open, 3 acknowledged). No critical finding is reported. Statuses are the security firms’ own.
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.
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.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="meta-things"></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