Normal behavior:
ERC20 tokens typically mint an initial supply during contract deployment to bootstrap liquidity, distribute to early contributors, or prepare for vault or staking operations.
Issue:
The BriTechToken contract constructor does not mint any tokens on deployment. The owner must later call mint() manually to create the initial supply, leaving the contract in an empty state after deployment.
This breaks expectations for automated integrations or token-based systems (like vaults or DEX pairs) that assume a non-zero supply at launch.
Likelihood:
This issue occurs every time the contract is deployed since the initial mint is omitted from the constructor.
It will cause operational failures in integrations that rely on token balance existence at deployment (e.g., ERC4626 vault initialization).
Impact:
External protocols integrating this token (vaults, liquidity pools, or DEXes) may fail due to zero supply or revert when reading balances.
If the owner delays minting or forgets to mint, the entire ecosystem relying on this token halts temporarily.
Explanation:
Right after deployment, the token’s totalSupply() equals zero, causing dependent systems to fail initialization.
Mint the initial supply in the constructor to align with ERC20 launch expectations.
Explanation:
Automatically minting an initial supply ensures smooth integration with vaults, exchanges, and other contracts that require non-zero liquidity at launch.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.