0x9f4909cc95fb870bf48c128c1fdbb5f482797632
As of 21 Nov 2026, Trustblock’s record holds 0x9f4909cc95fb870bf48c128c1fdbb5f482797632 on Ethereum as a contract of Guzzler. 1 audit report on Trustblock lists this address: CertiK, 25 Oct 2022. 22 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on Ethereum.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| Guzzler - Audit | CertiK | Not recorded (see the report) | Open |
3 High, 19 Low. In the firm’s own words; statuses are the firm’s, from each report.
In the contract `Ownable`, the role `owner` has the authority over the following function: - renounceOwnership() - transferOwnership() In the contract `GZLR`, the role `owner` has the authority over the following function: - enableTrading() - setAutomatedMarketMakerPair() - setProtectionSettings() - setGasPriceLimit() - disableTransferDelay() - airdropToWallets() - removeLimits() - excludeFromReward() - excludeFromMaxTransaction() - includeInReward() - excludeFromFee() - includeInFee() - setBuyFee() - setSellFee() - setMarketingAddress() - setLiquidityAddress() - setSwapAndLiquifyEnabled() - buyBackTokens() - transferForeignToken() Any compromise to these accounts may allow the hacker to manipulate the project through these functions.
The audit on Trustblock · Open the report```solidity=1137 uniswapV2Router.addLiquidityETH{value: ethAmount}( address(this), tokenAmount, 0, // slippage is unavoidable 0, // slippage is unavoidable liquidityAddress, block.timestamp ); ``` The `addLiquidity()` function calls the `uniswapV2Router.addLiquidityETH()` function with the `to` address specified as `liquidityAddress` for acquiring the generated LP tokens from the `GZLR-WETH` pool. As a result, over time the `liquidityAddress` address will accumulate a significant portion of LP tokens. If the `liquidityAddress` is an EOA (Externally Owned Account), mishandling of its private key can have devastating consequences to the project as a whole.
The audit on Trustblock · Open the reportAll of the `Guzzler` tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute `Guzzler` tokens without obtaining the consensus of the community.
The audit on Trustblock · Open the reportThe linked function only allows to set the state variable `transferDelayEnabled` and `limitsInEffect` to `false`. Once the linked function is called, the transfer delay will never be enabled.
The audit on Trustblock · Open the reportWe noticed that the contract is deployed on Ethereum, but the naming in the contract uses BNB in some places and ETH in some places.
The audit on Trustblock · Open the reportBoth `newOwner` and `futureOwner` are the addresses of `msg.sender`, and `futureOwner` is just a local variable and has no practical meaning.
The audit on Trustblock · Open the reportWhen transferring, if the contract account balance exceeds the set value of `overMinimumTokenBalance` and some other conditions are met, the repurchase operation will be executed. The balance of the contract will be divided according to a certain ratio, one part will be converted into BNB (one part will be used to add liquidity, the other part will be transferred to the `marketingAddress` address), and the other part will be used to add liquidity. The lp will be sent to `liquidityAddress` which can be set by owner.
The audit on Trustblock · Open the reportThe following functions are declared as `public` and are not invoked in any of the contracts contained within the project's scope. The functions that are never called internally within the contract should have external visibility. In the contract `Ownable`: - `renounceOwnership()` in L252 - `transferOwnership()` in L257 In the contract `GZLR`: - `approve()` in L807 - `setAutomatedMarketMakerPair()` in L876 - `setSwapAndLiquifyEnabled()` in L1426
The audit on Trustblock · Open the reportThe calculation formula of `tokenForLiquidity` in line 1096 indicates that the token used to exchange BNB is `1/2 liquidity + marketing`. Therefore, the BNB transferred to `marketingAddress` should also be allocated according to the ratio of `marketingTokensSwap/(1/2 * liquidityTokensToSwap + marketingTokensSwap)`.
The audit on Trustblock · Open the reportThe function that affects the status of sensitive variables should be able to emit events as notifications to customers. **contract `GZLR`** - `enableTrading()` - `setAutomatedMarketMakerPair()` - `setProtectionSettings()` - `setGasPriceLimit()` - `airdropToWallets()` - `excludeFromReward()` - `excludeFromMaxTransaction()` - `includeInReward()` - `excludeFromFee()` - `includeInFee()` - `setBuyFee()` - `setSellFee()` - `setMarketingAddress()` - `setLiquidityAddress()` - `buyBackTokens()` - `transferForeignToken()`
The audit on Trustblock · Open the reportThe **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.
The audit on Trustblock · Open the reportThe given input is missing the check for the non-zero address.
The audit on Trustblock · Open the reportThe linked variables are assigned only once, either during their contract-level declaration or during the `constructor`'s execution.
The audit on Trustblock · Open the reportA 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 back running (after the transaction being attacked) a transaction to sell the asset. The following functions are 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: - `swapTokensForBNB()` - `addLiquidity()` - `buyBackTokens()`
The audit on Trustblock · Open the reportWhen the `marketingAddress` and `liquidityAddress` are set to new values, the previous values are not removed.
The audit on Trustblock · Open the reportThe judgment condition `to != owner()` in line 1023 and the judgment condition in line 1010 are duplicated.
The audit on Trustblock · Open the reportThe return values of function `addLiquidityETH()` are not properly handled. ```solidity=1137 uniswapV2Router.addLiquidityETH{value: ethAmount}( address(this), tokenAmount, 0, // slippage is unavoidable 0, // slippage is unavoidable liquidityAddress, block.timestamp ); ```
The audit on Trustblock · Open the reportThe scope of the audit treats 3rd party entities as black boxes and assumes their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts, such as increasing fees of 3rd parties, migrating to new LP pools, etc.
The audit on Trustblock · Open the reportIn the following code snippet, `tokensIntoLiqudity` should be `tokensIntoLiquidity`. ```solidity=701 event SwapAndLiquify( uint256 tokensSwapped, uint256 ethReceived, uint256 tokensIntoLiqudity ); ```
The audit on Trustblock · Open the reportThe following events are declared but never used: - `RewardLiquidityProviders` - `SwapETHForTokens` - `SwapTokensForETH`
The audit on Trustblock · Open the reportFunction `getUnlockTime()` always return 0 because the variable `_lockTime` is never initialized.
The audit on Trustblock · Open the report1. The variable `_previousOwner` in line 229 is declared but never used or updated. 2. The variable `liquidityActiveBlock` in line 666 is declared but never used or updated. 3. The variable `tradingActiveBlock` in line 667 is declared but never used. 4. The variable `swapEnabled` in line 671 is declared but never used or updated.
The audit on Trustblock · Open the reportThe Guzzler security record · Every Guzzler address · This address on the explorer