0x1063181dc986F76F7eA2Dd109e16fc596d0f522A 0x1063...0f522A

Static analysis Dynamic analysis Symbolic Execution SWC check

CYBRIA is a Layer 2 blockchain platform built on top of the Ethereum network. It aims to enhance scalability, transaction speed, and security within the Ethereum ecosystem while leveraging Cybersecurity and Artificial Intelligence (AI) technologies to ensure network safety and improve performance CYBRIA is designed to address the limitations of the Ethereum network by providing a scalable, secure, and efficient Layer 2 solution. By utilizing Layer 2 scaling techniques, CYBRIA aims to reduce transaction costs and increase the throughput of the Ethereum network.

Contract address
Network Ethereum Mainnet
License None
Compiler v0.8.19 v0.8.19+commit.7dd6d404
Type N/A
Language Solidity
Request date 2023/08/11
Revision date 2023/08/14

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 renounced Contract cannot be manipulated by owner functions.

The following _taxWallet is currently set and cannot be renounced: 0x746b95fFe1BD7080169125F12e7d96BC09076E32

Owner privileges

  • The owner can set the fees but only reducing. The _finalBuy and _finalSellTax are set to 4 by default.
  • The owner can remove the limits

TaxWallet privileges

  • The taxWallet can call the manualSwap function

The added liquidity during the opening trade is locked for 12 Months. After it the "_taxWallet" owner can get out the liquidity. Locked:

Information for taxes during the transfer:

  • If the buyCount is below 25%, the "_initialBuyTax" (30%) will be set as fee; otherwise, the "_finalBuyTax" (4%) will be used
  • If the sellCount is below 25%, the "_initialSellTax" (30%) will be set as fee; otherwise, the "_finalSellTax" (4%) will be used

The "onlyOwner" function cannot be called because the owner is renounced (, but the EOA "_taxWallet" can call the "manualSwap" function. In the "manualSwap" function, the "swapAndLiquify" will be called. However, the "_taxWallet" will get the marketing part as ETH, and the liquidity will also be added to the "_taxWallet". Since the "_lpFee" is set to 0, the "addLiquidity" function will never be called.

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.



State variables


Total lines
of code


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


#1 Issue

Local variables shadowing (shadowing-local)





Rename the local variables that shadow another component.


#2 Issue

Missing Events Arithmetic (events-maths)




Emit an event for critical parameter changes.

informational Issues


#1 Issue

Unnecessary safemath library




Since the pragma version is 0.8.19, the overflow/underflow issue is handled by default. Replacing the SafeMath operations with raw mathematical operations is recommended.

optimization Issues


#1 Issue

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










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


#2 Issue

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











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


Disclaimer 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. do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...) 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. 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.