Metaegg Info
Metaegg working on web3 through NFT, Gaming, Entertainment, and DeFi. $MDEFI is a token made to support what’s next, controlled, and built on by the community. It will serve as a decentralized protocol layer for community-led initiatives that drive culture forward into the Metaverse Gaming & Lifestyle app project with inbuilt Game-Fi, Fit-Fi, and Social-Fi elements in one place. we are focusing on essential daily activities we all do in our life. We are the first project to effectively bring together the Play, Breed & Move to earn concept. Users equip themselves with NFTs. By playing, walking, jogging, or running within metaverse or gaming architecture, users will earn game currency, which can either be used in-game or cashed out for profit. With Game-Fi & Fit-Fi Metaegg aims to nudge millions toward a safer, healthier engaging lifestyle, combat climate change and connect the public to Web 3.0, all while simultaneously hinging on its Social-Fi aspect to build a long-lasting platform governed by its users.
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.
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.
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 cannot set high fees
The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Contract cannot be locked
Owner cannot lock any user funds.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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.
The Owner can do the following changes in the contract:
- Blacklist/Whitelist Addresses
- Set maximum transaction and wallet amount just above 0, for example, 1,2,3, etc, to slow down the transactions and let users hold only a few tokens in the wallet.
- Set AMM pairs
- Update gas for processing
- Pause/Unpause the contract
- Update reward token address
- Set the Balance of an account
- Process any account and withdraw dividend of user
- Update the waiting time for the claim of rewards but within a specified range
- Exclude wallets from dividends
- Distribute reward dividends manually at anytime
- Update the dividend tracker/router contract address at any point in time
- Set fee receiving addresses
- Set shares for buy and sell but only less than or equal to 5
On Line2149, Function swapTokensForReward cannot be WETH address because it will fail.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 7 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low Issue
Floating Pragma
The current pragma Solidity directive is “^0.8.15". Contracts should be deployed with the same compiler version and flag that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.
Pending
#5 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
Pending
#6 low Issue
Missing error message
Make sure to add an error message in require statements
Pending
#7 low Issue
Access Control
These functions should not be public
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 3 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
Pending
#3 informational Issue
Uninitialized local variables (uninitialized-local)
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.