Insanity Info
InsanityBets is not just a platform; it's the evolution of CasinoFi & GameFi, allowing you to become the house. As a non-custodial and decentralized platform, InsanityBets brings the casino experience directly to the blockchain.
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.
TrustNet DataPulse
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.
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 can mint
It is 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.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token can be burned
There is a function to burn tokens in 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:
- 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.
Ownership Privileges
- The governor's address can update the admins in the contract.
- The admin can mint an unlimited amount of tokens.
- The admin can burn an unlimited amount of tokens without any allowance.
- The governor's address can update the governor's address.
- The governor's address can update the name and symbol of the token.
- The governor can add the yield trackers to the contract.
- The governor can claim stuck tokens from the contract, including the contract's tokens.
- The governor can enable/disable private transfer mode in the contract.
- The governor can whitelist addresses for transferring tokens in private transfer mode.
- The admin can add or remove wallets from the non-staking list in the contract.
- The admin can claim the yield from the contract to any wallet.
Note - This Audit report consists of a security analysis of the Insanity 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 Insanity team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing. The contract implements one yield tracker contract, which is out of scope for the audit, and our team will not be responsible for any security concerns in that contract.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
high Issues | 2 findings
Pending
#1 high Issue
The minter can burn tokens without allowance.
The minter can burn the unlimited amount of tokens from any wallet without any allowance which is not recommended as this can cause the loss of funds for the user. There must be an allowance for which the minter can burn the tokens.
Pending
#2 high Issue
Transfer of tokens without allowance.
The handlers in the contract can transfer the tokens from other wallets without any allowance, and this is not recommended as this can cause the loss of funds. There should not be any address that can transfer the tokens from any particular wallet without any allowance.
medium Issues | 3 findings
Pending
#1 medium Issue
The owner can mint tokens,
The minter can mint an unlimited amount of tokens after the initial deployment, which is not recommended as this can manipulate the supply of tokens, and the user many lose his token values. It is recommended that there must be a fixed supply, and the minter cannot mint more than that particular amount.
Pending
#2 medium Issue
The owner can lock transferring of tokens.
The owner can enable/disable the transfer of tokens for un-whitelisted users, as this can lock the transfer of tokens, which is not recommended. It is recommended that there must be a locking period, and the owner cannot lock the transfer function for an unlimited period.
Pending
#3 medium Issue
The admin can drain tokens.
The admin can drain the yield tokens and transfer them to any particular wallet, which is not recommended as this can cause the loss of funds for the user.
low Issues | 3 findings
Pending
#1 low Issue
Old compiler version
Adding the constant latest 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 zero address validation.
Check that the address cannot be set to zero or dead address.
Pending
#3 low Issue
Missing events arithmetic
Emit all the critical parameter changes.