GOLDHEARTBnB Info
GOLD HEART BnB is here to change the DEFI space… GOLD represents the unlimited and endless value and benefits that the DEFI -space has brought to the world in general, the crypto space has marked a big change to age of man and civilization itself, a new finance/money method, set to change the future of 3rd parties(banks ) , it’s expansion will keep growing in the minds of people, and users in the long terms… HEART represents the immense love and the ultimate goal of giving back to the community and to the people, $GHB major aim is to give back to the people and eliminate poverty, we try to help as much people as we can through our buy back tax wallet for charity, a percentage of all trades goes to this wallet, which in turn goes to charity and general educational system in 3rd world countries
Overall Score
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
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 burn function within the contract.
Ownership is renounced
Contract cannot be manipulated by owner functions.
Scope of Work
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
- Include/Exclude wallets from rewards and fees
- Set fees without any limitations
- Enable/Disable Swap and Liquify
- Set max transaction percent to any arbitrary value including zero and lock user funds
The ownership has been renounced and the values mentioned above cannot be changed anymore.
Note - This Audit report consists of a security analysis of the GOLDHEARTBnB 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 GOLDHEARTBnB team, other contracts associated with the project were not audited by our team. We recommend investors to 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
medium Issues | 2 findings
Resolved
#1 medium Issue
Liquidity will be credited to an EOA
The liquidity of the contract is automatically added to the owner address which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
Resolved
#2 medium Issue
Fees can be 100% or more
The owner can set the tax fee up to 100% or more and if done so then it may lead to loss of user funds
low Issues | 3 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
State Variable Visibility not set
It is the best practice to set the visibility of state variables explicitly
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 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
Function initializing state variables (function-init-state)
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Pending
#3 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.
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:
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.