Discovery Trending Launches KYC Verified Watchlist Risk Alerts
Token Minter AI Threat Detection Token Burner
Blog & News Docs Visit SolidProof.io

Trust Bitcoin Info

trustbitcoin.io

Trust Bitcoin has an edge in DeFi services because of its best-in-class offerings. With the likes of services like mining, smart contracts, digital wallets, governance and creating dApps. Also, miners will have exceptional benefits for adding a block to the Trust Bitcoin blockchain.

Trust Bitcoin Logo
Onboarded date 24/06/2025

Team and KYC Verification

The KYC verification for this project is currently in progress.

The team has submitted their information and verification is pending.

KYC Badge

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.

0.03
Poor Excellent

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.

Security Assessments

Select the audit
"Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review"
Contract address
0xaDAe...1C8A
Network
BNB Smart Chain - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2026/03/23
Revision date 2026/03/23

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 cannot be burned

There is no burning within the contract without any allowances

Ownership is not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

Contract is not upgradeable

The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.

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.

Ownership Privileges
  • The DEFAULT_ADMIN_ROLE can add the liquidity pair.
  • The DEFAULT_ADMIN_ROLE can update the validator address.
  • The DEFAULT_ADMIN_ROLE can exclude wallets from fees.
  • The MINTER_ROLE can mint new tokens no more than the MAX_SUPPLY, which is set to 21_000_000 tokens.
  • The BURNER_ROLE can burn tokens from others wallets with allowance.

Note: Team Trust Bitcoin provided the contract file for this project. Afterward, they launched their own blockchain, TrustBitcoin. Any changes made after the audit are considered outside the scope of the audit, and the audit team holds no responsibility for those changes.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

Critical
High
Medium
Low
Optimization
3
Informational
informational Issues | 3 findings

Pending

#1 informational Issue
Floating pragma solidity version
WrappedTrustBitcoin.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.

Pending

#2 informational Issue
Incompatibility with Standard DEX Routers and Liquidity Provision Reverts
WrappedTrustBitcoin.sol
L147-169
Description

The contract implements a "Fee-on-Transfer" mechanism within the _transfer function, which automatically deducts a 1% tax (50 bps burn + 50 bps validator fee) whenever a transaction involves an address registered in the isLiquidityPair mapping. Standard Decentralized Exchange (DEX) Routers, such as UniswapV2 or PancakeSwap, are not designed to handle tokens that lose value during a transfer. During an addLiquidity call, the Router transfers a specific amount of tokens to the pool and then verifies if the pool's balance increased by that exact amount. Because this contract takes a fee during that transfer, the pool receives less than expected, causing the Router to trigger an immediate transaction revert (e.g., UniswapV2: K or INSUFFICIENT_OUTPUT).

Comments

To resolve this, the contract should ideally exclude the DEX Router or the "Liquidity Addition" process from being taxed. This is typically achieved by adding the router address to the isExcludedFromFees mapping during deployment. Additionally, the _shouldTakeFee logic should be refined to distinguish between a standard "Swap" (which should be taxed) and "Liquidity Provision" (which should not). If the tax must remain on all pool-related transfers, users and front-end interfaces must be explicitly instructed to use specialized SupportingFeeOnTransfer functions (e.g., swapExactTokensForETHSupportingFeeOnTransferTokens), though this will still not prevent the initial failure during liquidity addition.

Pending

#3 informational Issue
Unintentional Taxation on Liquidity Removal (Exit Fees)
WrappedTrustBitcoin.sol
L138-145
Description

The _shouldTakeFee function (Line 144) evaluates isLiquidityPair[from] as a condition to apply the 1% tax. When a liquidity provider (LP) decides to withdraw their capital from a DEX pool, the pool (from) sends the tokens to the user (to). Because the pool is marked as a liquidity pair, the contract mistakenly classifies this withdrawal as a taxable event. As a result, users are taxed 1% on their own principal when simply removing liquidity, which is a significant deviation from industry standards and common DEX behavior.

Comments

To resolve this, the contract should differentiate between "Selling to the pool" (Taxable) and "Withdrawing from the pool" (Non-Taxable). This is typically achieved by only applying the tax if the to address is a liquidity pair (on a Sell) OR if the from address is a liquidity pair AND the to address is not an authorized router/bridge. Alternatively, the contract can expose a function to temporarily disable fees for legitimate liquidity management operations conducted by the admin.