Boshi contract 0x33ad…8729 on Base

0x33ad778e6c76237d843c52d7cafc972bb7cf8729

As of 21 Nov 2026, Trustblock’s record holds 0x33ad778e6c76237d843c52d7cafc972bb7cf8729 on Base as a contract of Boshi. 1 audit report on Trustblock lists this address: CertiK, 30 May 2024. 3 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on Base.

AuditSecurity firmDateCommit named in the reportReport
Boshi Token - AuditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports3

1 High, 2 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighInitial Token DistributionBoshi Token - Audit · CertiKOpen

All of the Boshi tokens are sent to the `_owner` address. This is a centralization risk because the `_owner` can distribute tokens without obtaining the consensus of the community. Any compromise to the address may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

The audit on Trustblock · Open the report
LowPotential Sandwich AttacksBoshi Token - Audit · CertiKAcknowledged

A sandwich attack might happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (before the transaction being attacked) a transaction to purchase one of the assets and make profits by backrunning (after the transaction being attacked) a transaction to sell the asset. The following function is called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large: ```solidity=386 function swapTokensForEth(uint256 tokenAmount) private lockTheSwap { // generate the uniswap pair path of token -> weth address[] memory path = new address[](2); path[0] = address(this); path[1] = uniswapV2Router.WETH(); if(allowance(address(this), address(uniswapV2Router)) < tokenAmount) { _approve(address(this), address(uniswapV2Router), ~uint256(0)); } // make the swap uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens( tokenAmount, 0, // accept any amount of ETH path, marketingWallet, block.timestamp ); } ```

The audit on Trustblock · Open the report
LowThird-Party Dependency UsageBoshi Token - Audit · CertiKAcknowledged

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=279 IUniswapV2Router02 private uniswapV2Router; ``` ```solidity=304 IUniswapV2Router02 _uniswapV2Router = IUniswapV2Router02(0x6BDED42c6DA8FBf0d2bA55B2fa120C5e0c8D7891); ``` - The contract `Boshi` interacts with third party contract with `IUniswapV2Router02` interface via `uniswapV2Router`.

The audit on Trustblock · Open the report

The Boshi security record · Every Boshi address · This address on the explorer