Americoin Info

AmeriCoin emerges as a pioneering cryptocurrency designed to bridge the gap between blockchain technology and real estate investment. With a vision to democratize access to high-value property markets, AmeriCoin (AMERI) leverages the power of the BNB Smart Chain to offer a transparent, secure, and profitable investment ecosystem. Our mission is to empower individuals worldwide to participate in lucrative real estate opportunities, traditionally reserved for high-net-worth investors, through a decentralised and community-driven platform. By combining the stability of real estate with the flexibility of blockchain, AmeriCoin is poised to redefine how wealth is created and shared in the 21st century.

Americoin 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.

68.17
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
N/A
Network N/A
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/07/30
Revision date 2025/07/30

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.

Contract is not upgradeable

The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.

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 clear the stuck tokens from the contract.

Note - This Audit report consists of a security analysis of the Americoin 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 Americoin team. Other contracts associated with the project were not audited by our team. 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

low Issues | 1 findings

Pending

#1 low Issue
Owner can withdraw native AMERI tokens from the contract.
Americoin.sol
L97-106
Description

The AMERI contract at Americoin.sol inherits the rescueToken function from the StuckRecover contract (lines 93-109). This function is designed to allow the owner to recover ERC20 tokens that are accidentally sent to the contract address. However, this function also allows the owner to withdraw the contract's own AMERI tokens by passing the contract's address as the tokenAddress parameter. If users send AMERI tokens to the contract address, the owner can unilaterally retrieve them. This represents a centralization risk and may violate user expectations, as they might assume tokens sent to the contract are locked or being used for a specific purpose.

informational Issues | 2 findings

Pending

#1 informational Issue
Function that are not used (Dead code).
Americoin.sol
L9-11
Description

Remove unused code.

Pending

#2 informational Issue
Local variables shadowing (shadowing-local)
Americoin.sol
L172-176
L178-186
L205-220
L222-224
L310-316
Description

Rename the local variables that shadow another component.