Travenis
0x067a71B9499bd67e8C2761c01b26d787ed0938fe 0x067a...0938fe

Static analysis Dynamic analysis Symbolic Execution SWC check

We've recreated the world of GTA San Andreas with all the cities, landmarks, and characters that you know and love. It's like stepping into a time machine and reliving the glory days of gaming! But wait, there's more! "Travenis" is packed with side activities and mini-games, including street races, gang wars, roberries, running your own business, and more. The opportunities to earn $TRV tokens are endless! In short, "MTA: Travenis" is a faithful recreation of the classic game, now with a Metaverse twist! It's an immersive, engaging, and rewarding experience that's sure to leave fans of the original game grinning from ear to ear.

Contract address
0x067a...0938fe
Network Binance Smart Chain
License None
Compiler v0.8.14 v0.8.14+commit.80d49f37
Type N/A
Language Solidity
Request date 2023/03/07
Revision date 2023/04/14
Critical
Passed
High
Passed
Optimization
Passed

Owner privileges

Crucial issues found The contract does contain issues of high or medium criticality. In some circumstances, the Contract may not function as intended and may pose a safety risk.
Contract owner cannot mint It is not possible to mint new tokens.
Contract owner can blacklist addresses It is possible to lock user funds by blacklisting addresses.
Contract owner can set high fees Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
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 Privileges:

  • Enable/Disable trading
  • Include/Exclude accounts from rewards, and fees
  • Set taxes to any arbitrary value
  • Airdrop tokens from own account
  • Update marketing, Dev, and Pte wallet address
  • Enable/Disable the cooldown and set the cooldown period to any arbitrary value. If it is set to a very high number then no one will be able to make transfers
  • Update swap tokens at amount to any arbitrary value including zero
  • Blacklist Addresses
  • Set max transaction and wallet limit to any arbitrary value including zero, which will result in locking of user funds
  • Update router and pair address
  • Withdraw BNB, and any token from the contract's balance including the native ones. This makes the owner capable to drain the liquidity from the contract.

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

53

State variables
public

18

Total lines
of code

708

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.

medium Issues

Pending

#1 Issue

Fees can be 100% or more

TRAVENIS.sol

L352

L357

Description

The owner is able to set taxes to any arbitrary value which is not recommended because this will result in the loss of user funds if the tax is set so close to or above 100%

Pending

#2 Issue

Owner can drain liquidity

TRAVENIS.sol

L702

Description

The owner can drain liquidity because after the liquidity is added to the contract, the owner is able to withdraw it but, by default, the liquidity will be transferred to the owner's wallet

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

TRAVENIS.sol

L253

L478

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

TRAVENIS.sol

L653-656

L658-660

L681-684

L686-688

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

TRAVENIS.sol

L207-208

L640

L644

L648

L690

Description

Check that the address is not zero.

informational Issues

Pending

#1 Issue

Unused return values (unused-return)

TRAVENIS.sol

L594-607

Description

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

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.