FoxxToken Info

We understand that many of you simply don't have the time to stay constantly updated in the crypto world. Between Discord, our app, and countless trading opportunities, it can often feel overwhelming to keep up. This is especially true for newcomers who may find it challenging to be involved everywhere and catch the right moments for trades. This is where the $FOXX Token comes into play. ​ With the $FOXX Token, we cleverly leverage the hype surrounding meme tokens. Staying true to our motto, "Earn money while having fun," we aim not to take things too seriously while still keeping real utility in sight. Our goal is not to create just another pump-and-dump project, but rather to develop a token that provides long-term value.

FoxxToken Logo

Team and KYC Verification

The team has securely submitted their personal information to SolidProof.io for verification.

In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.

KYC BadgePinksale Compliant KYCGempad Compliant KYC

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.

79.38
PoorExcellent

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.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Select the audit
Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xaF98...2C36
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/09/21
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 can blacklist addresses

It is 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 burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

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 trigger the tax.
  • The owner can withdraw BNB from the contract.
  • The owner can burn their tokens.
  • The owner can blacklist a wallet.
  • The owner can include/exclude wallets from the whitelist.
  • The owner can set buy and sell fees up to 10%.
  • The owner can set the tax wallet address.
  • The owner can enable/disable trading.
Recommendations

To mitigate potential hacking risks, it is advisable for the client to manage the private key of the privileged account with care. We also recommend enhancing the security practices of centralized privileges or roles in the protocol by transitioning to a decentralized mechanism or smart contract-based accounts, such as multi-signature wallets.

Here are some suggestions for the client:

  • Consider using multi-signature wallets, such as Gnosis Safe, which require multiple parties to sign off on a transaction before it can be executed, providing an extra layer of security.
  • Implement a timelock with a delay of 48-72 hours for privileged operations, allowing time for community awareness.
  • Introduce a DAO/Governance/Voting module to increase transparency and user involvement in the project’s decision-making process.
  • Consider renouncing ownership after all critical operations are completed, to ensure that no further modifications to the state variables can be made.

Note - This audit report consists of a security analysis of the FOXX.sol smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited this contract for the FOXX project. Other contracts associated with the project were not audited by our team. We recommend that investors conduct their own research before investing.

Files and details

Findings and Audit result

medium Issues | 2 findings

Pending

#1 medium Issue
The owner can blacklist wallets.
FOXX.sol
L1078-1086
Description

The owner can blacklist wallets from transferring tokens for an unlimited period of time which is not recommended as this can lock the user's funds indefinitely. There must be a locking period in the contract so that the user should not be locked for an unlimited period of time.

Pending

#2 medium Issue
Missing ‘require’ check (Potential honeypot)
FOXX.sol
L1106-1112
Description

The owner can set any arbitrary address to the tax wallet address, excluding zero address as this can lead to a potential honeypot if the owner has set the address to a contract address that cannot receive ETH. It is recommended that the address cannot be set to a contract address that cannot receive ETH to avoid these circumstances.

low Issues | 2 findings

Pending

#1 low Issue
Floating pragma solidity version.
FOXX.sol
L7
Description

Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#2 low Issue
Missing events arithmetic.
FOXX.sol
L1078-1081
L1083-1086
L1098-1104
L1106-1112
L1114-1120
L1122-1125
L1127-1130
Description

Emit an event for critical changes.

informational Issues | 1 findings

Pending

#1 informational Issue
NatSpec Documentation missing.
All
-
Description

If you started to comment on your code, also comment on all other functions, variables, etc.