Sakai Vault Info

Sakai Vault is a decentralized spot and perpetual exchange that supports low swap fees and zero price impact trades. Trading is supported by a unique multi-asset pool that earns liquidity providers fees from market making, swap fees and leverage trading. Sakai Vault is a next crypto revolution and it is Accelerates DeFi Adoption With Trusted Blockchain Protocol and Unique Token Economics Sakai Vault Provides its customers and investors with insights on trends and developments in the crypto space. We provide an in-depth look at selected topics ranging from cryptocurrency fundamentals to market analyses and help to grow your investment with us.

Sakai Vault 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.

9.01
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
0xF138...3a0e
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/12/16
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
  • Claim Reward for any arbitrary account at any time
  • Withdraw non-native tokens from the smart contract
  • Update the minimum stake value for the vote, proposal creation, and reward
  • Update the percentage for claimable tax by the referrer
  • Update the Distribution Percentage for the Referrer.
  • Update the Tax values for the staking pool, and Vault Capital
  • Set/Update Staking Pool, Treasury, Vote, and Vault Capital Addresses

Note - This Audit report consists of a security analysis of the SakaiDAO Staking smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the contracts mentioned in the reports presented on this link for the Sakai team. Our team did not audit other contracts associated with the project. We recommend investors 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
Contracts locks ether
SakaiDAO.sol
L513
Description

The contract has the functionality to receive ETH/BNB but there is no function to remove it from the contract's balance. Hence, the ETH/BNB sent to the contract will be locked forever. Remove the payable attribute or add a withdraw function.

low Issues | 3 findings

Pending

#1 low Issue
Missing Events Arithmetic
SakaiDAO.sol
L902-905
Description

Emit an event for critical parameter changes.

Pending

#2 low Issue
Missing Zero Address Validation
SakaiDAO.sol
L488
Description

Check that the address is not zero.

Pending

#3 low Issue
Tautology or contradiction in comparison
SakaiDAO.sol
L606-625
L884-888
L890-894
L896-900
Description

Because of the uint data type of the parameters passed in the function, the condition inside the 'require' check is redundant since it can never be false. Fix the incorrect comparison by changing the value type or the comparison.

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used
SakaiDAO.sol
L66-69
L189-212
L380-382
L640-643
L691-699
Description

Remove unused functions.