SurgeUseless

In the contract `SurgeUSELESS`, the role `owner` has the authority over the following function: - function ActivateSurgeToken() - function enableEmergencyMode() - function setAllowSurgeStaking(bool allow) - function updateFundingValues(bool allowSurgeFunding, uint256 transferDenom, uint256 buySellDenom) - function updateSurgeFundAddress(address newSurgeFund) - function setIsApprovedLP(address LP, bool isLP) - function updateUseOfUselessBypass(bool useBypass) - function changeGarbageCollectorThreshold(uint256 garbageThreshold) - function transferOwnership(address newOwner) - function renounceOwnership() Any compromise to the `owner` account may allow the hacker to manipulate the project through these functions.

The SurgeUseless Protocol is a decentralized deflation token deployed on the Binance smart chain (BSC). The user can stake USELESS and BNB to obtain SUSLS. When the user transfers BNB into the contract, the contract will burn all the balance of SUSLS in the contract when the balance reaches `garbageCollectorThreshold`. The price of SUSLS = the USELESS balance of the contract / the total supply of SUSLS. When the user stakes/sells SUSLS, the transaction will charge 6% of the amount of SUSLS as the fee. When the user transfers SUSLS, the transaction will charge 4% of the amount of SUSLS as the fee. If `allowFunding` is true, some of the fees will be given to `_surgeFund`, and the remaining will be burned. It should be noted that whether it is the purchase, sale or transaction, the exchange ratio between USELESS and SUSLS will change. If the operation charges the fee, the price of SUSLS will rise, and the price of SUSLS will remain unchanged if no fee is charged.

The contract is serving as the underlying entity to interact with third-party UselessSwapper protocols. The 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.