MAROSCA Info

Marosca is a MEME project named after world-famous soccer player Cristiano Ronaldo's beloved dog. It combines blockchain technology and soccer sports culture to create a unique and attractive digital ecosystem that soccer fans and blockchain enthusiasts from around the world can meet. We are devoted to It will be the intersection of soccer fans and blockchain enthusiasts from around the world.

MAROSCA Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

13.87
Poor Excellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xf9f8...fa92
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/05/24
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

Contract owner cannot mint

It is not possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner can set high fees

Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.

Token transfer can be locked

Owner can lock user funds with owner functions.

Token cannot be burned

There is no burning within the contract without any allowances

Ownership is not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


Ownership Privileges
  • The owner can enable trading but cannot disable it.
  • The owner can remove limits.
  • The owner can update the total buy and sell fee to 100%.
  • The owner can update the max transaction and max wallet amount to an arbitrary value, including zero, which may result in the contract being a honeypot
  • Include/Exclude wallets from max tx limits and fees
  • Set Marketing and Team wallet address
  • Enable/Disable swap and liquify

Note - This Audit report consists of a security analysis of the MAROSCA Token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the MAROSCA team. Our team did not audit other contracts associated with the project. We recommend investors do their own research before investing.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

high Issues | 1 findings

Pending

#1 high Issue
The owner can set Arbitrary Fee
Marosca.sol
L467
L480
Description

The owner can set fees up to 100% or more, which is not recommended because if done so, then all the user funds will be lost during buying/selling.

medium Issues | 2 findings

Pending

#1 medium Issue
The owner can lock contract (Potential Honeypot)
Marosca.sol
L496
L508
L595
Description

The owner can set the max transaction and max wallet limit to a very low number or even zero, which will result in the contract becoming a honeypot because no user will be able to transfer their funds.

Pending

#2 medium Issue
Liquidity is Transferred to the owner address
Marosca.sol
L723
Description

The liquidity is automatically credited to the owner's address, which is not recommended as it may cause the owner to drain all the liquidity

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing
Marosca.sol
L342
L410
L433
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic
Marosca.sol
L453-455
L457-460
L462-465
L467-473
L475-478
L480-486
L488-494
L496-498
L508-510
L512-514
L530-532
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation
Marosca.sol
L342
L343
L344
L345
L517
L521
Description

Check that the address is not zero.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant
Marosca.sol
L263
L264
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external
Marosca.sol
L152-154
L161-164
L166-170
L172-174
L390-392
L394-396
L398-400
L402-404
L410-412
L414-417
L419-422
L424-426
L428-431
L441-443
L449-451
L453-455
L457-460
L462-465
L475-478
L525-528
L530-532
L534-536
L538-542
L545-547
L553-570
L575-578
L580-584
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used
Marosca.sol
L126-143
L109-111
L113-115
L117-119
L121-124
L90-99
L101-107
L10-14
L713-726
L549-551
L78-80
L82-85
Description

Remove unused functions.