Scorpion Casino Info

scorpion.casino

The SCORPION ecosystem is the one-stop play-to-earn decentralized gambling platform, providing more than 30,000 betting opportunities per month, 210 casino games, and 160 live games with a licensed, transparent, and provable platform.

Scorpion Casino Logo

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.

On-Chain Insights

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xa910...4b10
Network BNB Smart Chain - Mainnet
License N/A
Compiler N/A N/A
Type N/A
Language Solidity
Onboard date 2024/04/10
Revision date In progress

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 not renounced

Contract can be manipulated by owner functions.

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 exclude/include wallets in rewards.
  • The owner can exclude/include wallets in fees.
  • The owner can update the total sell fee to not more than 10%.
  • The owner can update the marketing wallet address.
  • The owner can update the minimum swap threshold amount to not less than 10000.
  • The owner can enable/disable swapping.

Note - This Audit report consists of a security analysis of the Scorpion Casino 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 Scorpion Casino team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.

Scope of Work

Files and details

This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.

The auditing process follows a routine series of steps:
  1. Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
  2. Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  3. Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  4. Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  5. Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
  6. Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
  7. Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been intentionally or otherwise modified 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.

Findings and Audit result

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
SCORP.sol
L277
L663
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
SCORP.sol
L446-462
L469-475
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Remove safemath library
SCORP.sol
L35-74
Description

The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.

medium Issues | 1 findings

Pending

#1 medium Issue
Missing 'require' check
SCORP.sol
L464-467
Description

The owner can update any arbitrary wallet as the marketing wallet address, excluding zero, as this can cause the loss of funds if the owner sets the marketing wallet to a dead address or to any contract address that cannot receive BNB. It is recommended to check that the address is not dead or a contract address.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
SCORP.sol
L84
L179
L177
L178
L176
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
SCORP.sol
L105-108
L110-117
L247-249
L251-253
L255-257
L259-261
L268-275
L277-284
L286-293
L295-310
L312-323
L325-339
L341-343
L345-347
L349-359
L361-374
L389-396
L435-438
L440-444
L658-660
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 2 findings

Pending

#1 informational Issue
Costly operations in a loop (costly-loop)
SCORP.sol
L398-409
Description

Use a local variable to hold the loop computation result.

Pending

#2 informational Issue
Functions that are not used (dead-code)
SCORP.sol
L63-72
Description

Remove unused functions.