Layer GPT
0x36f69C5Ad047A0b689Ed833c8aC410caefC24792 0x36f6...C24792

Static analysis Dynamic analysis Symbolic Execution SWC check

LayerGPT is a layer-2 that uses zkRollup technology. The unique EVM-compliance makes the protocol open to massive codebase libraries, enabling easy and rapid onramp of developers and users. LayerGPT is carefully designed to be a network uncontrollable by centralized influence. The mining model and security align with activity. Incorporating remarkable scalability and remarkably affordable transactions, LayerGPT offers a robust infrastructure encompassing data, AI tools, and a versatile earning platform.

Contract address
0x36f6...C24792
Network Binance Smart Chain
License MIT
Compiler v0.8.9 v0.8.9+commit.e5eed63a
Type N/A
Language Solidity
Request date 2023/10/24
Revision date 2023/10/24
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

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

Ownership Privileges

  • The owner can enable trading only once.
  • The owner can air-drop tokens to multiple wallets at once.
  • The owner can enable/disable swapping.
  • The owner can enable/disable rescue swap. Once it is enabled, the contract balance will be transferred to the marketing wallet address when the swapping is completed.
  • The owner can update buy, sell, and transfer fees of not more than 10%.
  • The owner can exclude wallets from fees.
  • The owner can update the automated market maker pair address.
  • The owner can update the marketing wallet address.
  • The owner can reset the tax amount.

Note - This Audit report consists of a security analysis of the Layer GPT 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 Layer GPT team, other contracts associated with the project were not audited by our team. We recommend investors to 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

96

State variables
public

18

Total lines
of code

1223

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.

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

LayerGPT.sol

L916

L920

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

LayerGPT.sol

L1017-1022

L1024-1029

L1031-1036

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

LayerGPT.sol

L1055

Description

Check that the address is not zero.

Pending

#4 Issue

Floating pragma solidity version.

LayerGPT.sol

L3

Description

Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

LayerGPT.sol

L10-13

L398-406

L575-577

L591-594

L699-702

L690-694

L670-676

L658-665

L681-685

L705-708

L712-716

Description

Remove unused functions.

Pending

#2 Issue

Unused state variables (unused-state)

LayerGPT.sol

L653

Description

Remove unused state variables.

optimization Issues

Pending

#1 Issue

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

LayerGPT.sol

L205-207

L213-215

L230-232

L237-239

L256-259

L264-266

L275-278

L293-301

L315-318

L334-337

L614-616

L633-636

L1177-1180

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.