Galactic Goat Info

Welcome to GOAT Token – the most entertaining, community-driven meme coin on the blockchain. We’re not here to reinvent the wheel but to bring joy, laughter, and a unique sense of belonging to the crypto world.

Galactic Goat 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.

50.71
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
0x1AE6...8076
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/01/02
Revision date 2025/01/02

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 deploy a new version of the contract which can change any limit and give the owner new privileges
  • The ERC20 Token is an upgradeable contract in the dividend tracker
  • Deployer can set the following state variables without any limitations
    • swapTokensAtAmount
    • minimumTokenBalanceForDividends
  • Deployer can enable/disable the following state variables
    • _isExcludedFromFees
    • excludedFromDividends
  • Deployer can set the following addresses
    • _marketingWalletAddress
  • Existing Modifiers
    • onlyOwner
    • initializer

Note - This Audit report consists of a security analysis of the Galactic Goat 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 Galactic Goat team, other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing. Also, we cannot verify if the contract is deployed using a proxy.

Files and details

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
BABYTOKEN.sol
L2458
L2459
L2519
L2526
L2538
L2552
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
BABYTOKEN.sol
L3068-3074
L3106-3110
L3112-3116
L3118-3122
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
BABYTOKEN.sol
L3039-3040
L3005
Description

Check that the address is not zero.

Pending

#4 low Issue
Local variables used prior their declaration (variable-scope)
BABYTOKEN.sol
L3346
L3348
L3347
Description

Move all variable declarations prior to any usage of the variable, and ensure that reaching a variable declaration does not depend on some conditional if it is used unconditionally.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
BABYTOKEN.sol
L203-205 ,211-213
L228-230 ,254-257 ,262-264
L273-276 ,291-305 ,319-322 ,338-346 ,873-875
L881-884 ,1748-1750 ,1756-1758 ,1773-1775 ,1799-1802 ,1807-1809 ,1818-1821 ,1836-1850 ,1864-1867 ,1883-1891 ,2105-2107 ,2113-2116 ,2280-2282 ,2284-2293 ,2295-2301 ,2303-2305 ,2466-2477
L2670-2675
L2519-2521
L2538-2545
L2687-2693
L2772-2793
L2820-2872
L3138-314
L3178-3180
L3182-3188
L3190-3196
L3202-3208
Description

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)
BABYTOKEN.sol
L579-581 ,608-614 ,668-670 ,678-687 ,641-643 ,651-660 ,554-559 ,1165-1174 ,1199-1205 ,1179-1194 ,136-138 ,1664-1666 ,1674-1676 ,2571-2586 ,416-431 ,1907-1927 ,763-776 ,787-798 ,778-785 ,747-754 ,1084-1093 ,1044-1046 ,1110-1119 ,1061-1070 ,915-921 ,957-962 ,969-974 ,940-950 ,928-933
L2238-2241 ,2209-2215 ,2197-2204
Description

Remove unused functions.

Pending

#2 informational Issue
Conformity to Solidity naming conventions (naming-convention)
BABYTOKEN.sol
L1280 ,1664-1666 ,1668-1669 ,1677 ,1735-1738 ,1740-1743 ,2042 ,2074-2077 ,2079-2081 ,2123 ,2146 ,2147 ,2164 ,2456-2464 ,2457 ,2458 ,2459 ,2519 ,2526 ,2538 ,2552 ,2436 ,2723 ,2960
Description

Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).

Pending

#3 informational Issue
Unused state variables (unused-state)
BABYTOKEN.sol
L2192 ,2123
Description

Remove unused state variables.