metaruffy.io has 1 public audit report from CertiK; dated 28 Sep 2022; 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
9 findings are still open or acknowledged in the firms’ reports: 2 high, 7 low (all open).
Centralization Risks in METARUFFY.sol
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Initial Token Distribution
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Potential Blending of Ether
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
State Variable Should Be Declared Constant
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Third Party Dependency
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Too Many Digits
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Typo
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Unclear Error Message
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Unnecessary Use of SafeMath
Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Meta Ruffy - Audit 3 | Security firm: CertiK | Date: | Scope: 1 address on Ethereum | None open | Findings: 2 high · 8 low 1 fixed · 9 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 2 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 7 | 0 | 1 |
In the contract `METARUFFY` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of the following: - Set new receivers to get ether from swaps if passed the threshold. - Update the divider between the marketing and developer wallet. - Change the burn, developer, and marketing fee. - This would allow the malicious user to set the burn fee to zero and maximize token gain for themselves. - Change the threshold for swaps to maximize ether gained into their wallets. - Enable the antiSnipe bot for transactions. ---  In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this and transfer or renounce ownership. 
Open the reportWhen deploying `MetaRuffy`, all the tokens are sent to the contract deployer. This could be a centralization risk as the team can distribute tokens without obtaining the consensus of the community.
Open the reportIf a user sends ether to the smart contract, then it has to wait until a transfer function calls `swapAndSendEth()` to have the funds sent to the marketing and dev wallet.
Open the reportState variables that never change should be declared as `constant` to save gas. ```solidity=566 uint256 _totalSupply = 300 * 10 ** 9 * (10**_decimals); ``` - `_totalSupply` should be declared `constant`.
Open the reportThe contract is serving as the underlying entity to interact with one or more third party AMM and PinkAntiBot protocols. 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=580 IPinkAntiBot public pinkAntibot; ``` - The contract `METARUFFY` interacts with third party contract with `IPinkAntiBot` interface via `pinkAntibot`. The `pinkAntibot` directly influences how the `transfer()` function works and can lead to unintended consequences if an error occurs.
Open the reportLiterals with many digits are difficult to read and review. ```solidity=563 address constant public DEAD = 0x000000000000000000000000000000000000dEaD; ```
Open the reportThe event and emit for "UpdateMarketingDevider" is spelled incorrectly.
Open the reportThe following error message(s) could be interpreted as unclear: ```Solidity=727 require(_marketingFee.add(_devFee).add(_burnFee) <= 10, "METARUFFY: Max fee limit exceeds"); ``` --- ```Solidity=787 require(_marketingFeeReceiver != address(0), "METARUFFY: zero address passed"); require(_devFeeReceiver != address(0), "METARUFFY: zero address passed"); ``` --- ```Solidity=824 require(_newPercent >= 25, "Marketing divider is low."); ```
Open the reportThe `SafeMath` library is used unnecessarily. With Solidity compiler versions 0.8.0 or newer, arithmetic operations will automatically revert in case of integer overflow or underflow.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0xa4cb…29aa0xa4cb3ef5f41a4d89d6fced22ea8a1c57957629aa | Chain: Ethereum | Source code: Verified source |
Trustblock holds 1 public audit report for metaruffy.io, dated 28 Sep 2022. The latest is by CertiK (“Meta Ruffy - Audit 3”).
CertiK wrote the report Trustblock holds for metaruffy.io.
9 findings are still open or acknowledged in the firms’ reports: 2 high, 7 low (all open). 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="metaruffy"></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