Texas Protocol Info

TBA

Texas Protocol 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.

88.61
PoorExcellent

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.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xCC14...Dc58
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/09/21
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 can be burned

There is a function to burn tokens in the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

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.


The owner can:

  • Withdraw the tokens from the SwapHelper contract
  • Approve any token address for a certain amount
  • Exempt fee receiver address and Remove accounts from fees mapping
  • Set Developing wallets
  • Set buy back and hold amount/address (also with decimals)
  • Buy back and burn with/without decimals
  • Set WBNB Token Pair
  • Set WBNB/BUSD Pair
  • Grant permission to other accounts for the following roles: "Admin", "Financial", "Controller", and "Operator"
  • The wallets with admin permission can; withdraw tokens from the contract and approve other tokens.
  • Due to the Authorized contract, there will be an admin in the contract even after renouncing the ownership because there can be multiple authorities controlling the contract. Moreover, only the wallets with 'admin' permission can revoke the role

Renouncing ownership will not affect the admin privileges of the wallets and there can be 'n' number of wallets that can be authorized for admin and other privileges because there is no protection from it. Thus, there is no maximum number of wallets that can have multiple authorizations over the contract.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 7 findings

Pending

#1 low Issue
Missing Zero Address Validation (missing-zero-check)
TexasProtocol.sol
L65
L66,180,182
L314
L315
Description

Check that the address is not zero.

Pending

#2 low Issue
State variables shadowing (shadowing-state)
TexasProtocol.sol
L17
L18
Description

Remove the state variable shadowing.

Pending

#3 low Issue
Missing Events
TexasProtocol.sol
All
Description

Emit events for critical parameter changes. There are no events in the contract

Pending

#4 low Issue
Floating Pragma
TexasProtocol.sol
L3
LExists in all Files
Description

The current pragma Solidity directive is “^0.8.15". Contracts should be deployed with the same compiler version and flag that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.

Pending

#5 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
TexasProtocol.sol
-
Description

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

Pending

#6 low Issue
Admin can drain tokens
Authorized.sol
L33
Description

Owner/Wallets with admin permission can withdraw the native tokens from the contract

Pending

#7 low Issue
Owner can drain tokens
SwapHelper.sol
L13
Description

Owner can also withdraw the native tokens from the contract

optimization Issues | 3 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
Ownable.sol
L53-55
L61-64
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
TexasProtocol.sol
L61
L62
L65
L66
Description

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

Pending

#3 optimization Issue
Public function that could be declared external (external-function)
ERC20.sol
L61-63
L69-71
L86-88
L93-95
L100-102
L112-115
L120-122
L131-134
L149-163
L177-180
L196-204
Description

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

informational Issues | 5 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
Context.sol
L20-22
L20-22
Description

Remove unused functions.

Pending

#2 informational Issue
Functions that are not used (dead-code)
Strings.sol
L39-50
Description

Remove unused functions.

Pending

#3 informational Issue
Functions that are not used (dead-code)
ERC20.sol
L274-289
L251-261
Description

Remove unused functions.

Pending

#4 informational Issue
Unused state variables (unused-state)
TexasProtocol.sol
L13
Description

Remove unused state variables.

Pending

#5 informational Issue
Unused return values (unused-return)
Authorized.sol
L29-31
L29-31
Description

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