metaruffy.io audit reports

Ethereummetaruffy.io

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.

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 firm9

Statuses are the security firms’ own

9 findings are still open or acknowledged in the firms’ reports: 2 high, 7 low (all open).

High
2
Low
7
  • High Open

    Centralization Risks in METARUFFY.sol

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • High Open

    Initial Token Distribution

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • Low Open

    Potential Blending of Ether

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • Low Open

    State Variable Should Be Declared Constant

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • Low Open

    Third Party Dependency

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • Low Open

    Too Many Digits

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • Low Open

    Typo

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • Low Open

    Unclear Error Message

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

  • Low Open

    Unnecessary Use of SafeMath

    Meta Ruffy - Audit 3 · CertiK · 28 Sep 2022 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Meta Ruffy - Audit 3Security firm: CertiKDate: Scope: 1 address on EthereumNone openFindings: 2 high · 8 low
1 fixed · 9 open
skynet.certik.com ↗

Findings10

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

SeverityOpenAcknowledgedFixed
Critical000
High200
Medium000
Low701
HighCentralization Risks in METARUFFY.solMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

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. --- ![](https://accelerator-tasks-prod.acc.corp.certik.com/f500e2a8e5e8411da7b9797c684bb082/diagrams/centralization_METARUFFY-METARUFFY-_owner.svg) 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. ![](https://accelerator-tasks-prod.acc.corp.certik.com/f500e2a8e5e8411da7b9797c684bb082/diagrams/centralization_METARUFFY-Ownable-_owner.svg)

Open the report
HighInitial Token DistributionMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

When 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 report
LowPotential Blending of EtherMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

If 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 report
LowState Variable Should Be Declared ConstantMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

State 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 report
LowThird Party DependencyMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

The 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 report
LowToo Many DigitsMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

Literals with many digits are difficult to read and review. ```solidity=563 address constant public DEAD = 0x000000000000000000000000000000000000dEaD; ```

Open the report
LowTypoMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

The event and emit for "UpdateMarketingDevider" is spelled incorrectly.

Open the report
LowUnclear Error MessageMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

The 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 report
LowUnnecessary Use of SafeMathMeta Ruffy - Audit 3 · CertiK · 28 Sep 2022Open

The `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

Contracts1

AddressChainSource code
0xa4cb3ef5f41a4d89d6fced22ea8a1c57957629aaChain: EthereumSource code: Verified source

metaruffy.io: questions

Is metaruffy.io audited?

Trustblock holds 1 public audit report for metaruffy.io, dated 28 Sep 2022. The latest is by CertiK (“Meta Ruffy - Audit 3”).

Who audited metaruffy.io?

CertiK wrote the report Trustblock holds for metaruffy.io.

Are there open findings in metaruffy.io’s audits?

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.

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="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