Seal (SEAL) security report
Radar by SecureChain AI-scanned Seal on Ethereum. The verified token is a fixed-supply OpenZeppelin ERC20 with no owner controls, taxes, blacklist, upgradeability, or post-deployment minting. A medium-severity risk is that the constructor assigns the entire supply to one recipient without on-chain vesting.
No critical or high-severity exploit was identified in the verified token source. The main material risk is the unrestricted initial allocation: the deployment recipient receives the full supply and can transfer it without token-level controls. The token itself has no privileged post-deployment administration or dynamic supply controls.
Trust score: 82/100. Source verified: Yes. Chain: ethereum. Contract: 0x1a9a7232599ec27a75138d2570aa829d1c3bcdd8.
This report was last modified on 2026-10-07 and contains 1 material finding.
medium finding: Entire supply is assigned to one constructor recipient without vesting
The constructor mints the complete supplied quantity directly to the address passed as `to`. The token contract has no vesting, timelock, allocation cap, or distribution rule that limits how that recipient can transfer the tokens. If the recipient is compromised or acts contrary to expectations, token distribution can be materially disrupted.
Evidence: `LockToken` constructor: `constructor(..., address to, uint256 supply) ... { _mint(to, supply); }`. The inherited OpenZeppelin ERC20 implementation permits the recipient to use `transfer` or approve another spender through the standard ERC20 functions. No later vesting, lock, or administrative distribution logic exists in the verified source.
Recommendation: Verify the constructor recipient and any external sale or distribution mechanism before relying on the token. If controlled distribution is required, use a separately audited vesting or timelock contract and document the allocation process.