Smart Staking Info

Smart Staking is a thoughtfully designed ecosystem created with the vision of amalgamating the best elements of transactional dividends, deflationary mechanisms, and staking benefits. By choosing Smart Staking, you are aligning with a project that emphasizes both immediate rewards and long-term value generation. The road ahead is paved with innovation, commitment, and a relentless pursuit of delivering unparalleled value to our community

Smart Staking 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.

35.09
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

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x9E67...A6C8
Network
BNB Smart Chain - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/01/27
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 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.

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
  • Include/Exclude wallets from dividends and fees
  • Update Claim Wait time
  • Update Marketing Wallet address, Max Wallet, and Max Transaction amount
  • Update buy/sell tax
  • Set/Update dividend tracker, dev wallet and Uniswap router address
  • Withdraw stuck BNB from the contract balance

Note - This Audit report consists of a security analysis of the SmartStaking 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 SmartStaking team. Our team did not audit other contracts associated with the project. 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 | 1 findings

Pending

#1 medium Issue
Missing 'require' check (potential honeypot)
SmartStaking.sol
L1405-1413
Description

The owner can update any arbitrary address as a marketing and dev wallet address, excluding zero address, as this leads to a potential honeypot if the owner has set the addresses to the contract address that cannot receive ETH. It is recommended that the address cannot be a contract address that cannot receive ETH.

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing
SmartStaking.sol
L587
L587
L637
L644
L651
L661
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic
SmartStaking.sol
L1399-1403
L1415-1424
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation
SmartStaking.sol
L1379-1380
Description

Check that the address is not zero.

informational Issues | 3 findings

Pending

#1 informational Issue
Functions that are not used
SmartStaking.sol
L20-23
L671-677
L1113-1115
L1129-1132
L1213-1216
L1184-1190
L1172-1179
Description

Remove unused functions.

Pending

#2 informational Issue
Function initializing state variables
SmartStaking.sol
L1263
Description

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
SmartStaking.sol
L1513-1515
L1526-1604
L1677-1692
Description

Ensure that all the return values of the function calls are used.