Contract risk checklist — bsc

Contract risk checklist — bsc

• ✔Contract source code is verified1 of 1 configured contract(s) publish verified source on the explorer. Verified source lets the published code be compared with deployed bytecode; it is not proof the code is safe.View sale contract
• ✘Sale and token contracts have independent deployersA single deployer wallet created every configured contract, which concentrates deployment and upgrade control in one party. It is a risk indicator, not proof of fraud.View deployer
• ✘Contract logic cannot be replaced through a proxyThe sale contract is an upgradeable proxy. Whoever controls the proxy admin may replace the implementation and change sale behaviour.View proxy contract
• ✔Proxy implementation source is verified1 of 1 resolved implementation contract(s) publish verified source. Unverified implementation logic cannot be audited.View implementation
• ✘Sale contract still holds the observed native fundsObserved native value has left the sale contract toward configured team wallets. Destination transfers must be reviewed to determine its use.View sale contract