8453 Trenchors (Trenchors) security report
Radar by SecureChain AI scanned the verified 8453 Trenchors contract on Base. The source uses a fixed initial mint and renounces ownership, with no detected administrative trading controls. A medium-severity allocation risk remains because the full initial supply is assigned to one constructor receiver without vesting.
No direct theft, mint-after-deployment, fee-manipulation, blacklist, pause, proxy, or honeypot mechanism was identified in the verified source. The main material risk is that the constructor sends the full configured supply to one receiver, leaving distribution dependent on that address and outside the contract’s controls.
Trust score: 92/100. Source verified: Yes. Chain: base. Contract: 0x73dfaac3f78d2708d533b248c71c96ffe98fef51.
This report was last modified on 2026-10-08 and contains 1 material finding.
medium finding: Entire initial supply is assigned to one receiver without vesting controls
The constructor mints the complete configured supply directly to receiver_. The token has no vesting, release schedule, allocation limits, or contract-enforced distribution mechanism. The receiver can therefore control transfers of the initially minted supply according to its own operational decisions.
Evidence: BaseToken constructor calls _mint(receiver_, supply_) after initializing ownership with Ownable(receiver_). No vesting contract, allocation split, timelock, or supply-distribution logic appears elsewhere in the verified source.
Recommendation: Document the intended allocation and receiver role. If distribution commitments are material, use a dedicated vesting or timelock contract and separate allocations before deployment; otherwise disclose that the initial supply is controlled by the constructor receiver.