Insanity
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.
Owner privileges
Comments
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.
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
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
/
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
high Issues
Pending
#1 Issue
The minter can burn tokens without allowance.
L28-30
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 Issue
Transfer of tokens without allowance.
L143-152
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
Pending
#1 Issue
The owner can mint tokens,
L24-26
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 Issue
The owner can lock transferring of tokens.
L78-80
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 Issue
The admin can drain tokens.
L100-105
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
Pending
#1 Issue
Old compiler version
L3
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 Issue
Missing zero address validation.
L52-54
Check that the address cannot be set to zero or dead address.
Pending
#3 Issue
Missing events arithmetic
L52-54
L56-59
Emit all the critical parameter changes.
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.