DeeLance
0x7D60dE2E7D92Cb5C863bC82f8d59b37C59fC0A7A 0x7D60...fC0A7A

Static analysis Dynamic analysis Symbolic Execution SWC check

Deelance is a freelancing and Recruitment platform based on Web3. Deelance is one such decentralized platform that is redefining how freelancers connect with potential employers and buyers

Contract address
0x7D60...fC0A7A
Network Ethereum Mainnet
License MIT
Compiler v0.8.17 v0.8.17+commit.8df45f5f
Type N/A
Language Solidity
Request date 2023/02/21
Revision date 2023/02/23
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

No critical 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.
Token transfer can be locked Owner can lock user funds with owner functions.
Token cannot be burned There is no burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
Comments

Ownership/Authority Privileges:

The authority other than the owner known as Verifier will be decided at the time of deployment and it can only be changed when the owner and the verifier itself vote. But even after the voting it will be upon the owner's discretion to set the verifier.

The verifier address has no privileges but the verifier's vote can decide whether the owner will be able to make transfers or not.

The owner has the following privileges:

  • Enable/Disable antiDump and antiBot
  • Set antiDump interval and amount to any arbitrary value.
  • Include/Exclude wallets from fees and  excluded wallets will also not be affected by the max transaction
  • Set the max transaction amount to any arbitrary value including zero to lock user funds that are not excluded from the fees.
  • Set fee wallet, and Enable/Disable fees
  • Start and Stop Trading to lock user funds
  • Set AMM pair address
  • Recover ETH and other tokens from the contract.

We recommend investors/users do their own research before investing

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)
The auditing process follows a routine series of steps:
  • 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

105

State variables
public

22

Total lines
of code

1381

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 specification 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.

low Issues

Pending

#1 Issue

Missing Events Access Control (events-access)

DeeLance.sol

L1210-1215

Description

Emit an event for critical parameter changes.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

DeeLance.sol

L1162-1165

L1192-1195

L1197-1200

L1202-1204

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

DeeLance.sol

L1172-1173

L1206

Description

Check that the address is not zero.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

DeeLance.sol

L475-477

L1365-1380

L953-969

L423-428

L387-389

L445-450

L404-409

L258-264

L300-305

L312-317

L283-293

L271-276

Description

Remove unused functions.

Pending

#2 Issue

Unused return values (unused-return)

DeeLance.sol

L1365-1380

Description

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

optimization Issues

Pending

#1 Issue

State variables that could be declared constant (constable-states)

DeeLance.sol

L1074

L1090

L1071

Description

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

Pending

#2 Issue

Public function that could be declared external (external-function)

DeeLance.sol

L541-543

L549-552

L738-740

L746-748

L763-765

L770-772

L789-793

L812-816

L834-839

L853-857

L873-882

L1167-1175

L1184-1190

L1206-1208

L1210-1215

L1222-1224

L1226-1228

L1244-1248

L1258-1260

L1354-1357

L1360-1363

Description

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

Diagrams

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.