The contract implements a double-precision multiplier (10¹⁸ in constructor + implicit 10¹⁸ in fee calculation) without compensating division. While mathematically consistent with the code, this approach:
Forces deployers to use counterintuitive fee values
Requires deployers to calculate fees as desired_wei / 10¹⁸
Creates 10¹⁸x mismatch between natural inputs and actual economics
Economic Model Failure: Token pricing becomes impractical
Deployer Errors: Guaranteed misconfiguration due to unnatural input requirements
Protocol Viability: Real-world usability destroyed unless deployer understands hidden precision requirement
Likelihood:
• 100% of deployments affected
• Natural inputs cause catastrophic errors
• Requires precise counterintuitive math
Impact:
• Permanent economic failure if misconfigured
• Requires redeployment to correct
• Financial losses guaranteed
Normal Deployment Scenario (Disaster):
Deployer wants 0.01 ETH/token
Sets _buyFee = 0.01 * 10¹⁸ = 10¹⁶
(natural wei conversion)
Actual fee per token:
Exceeds global ETH supply
Correct Input (Unnatural):
Deployer wants 1 ETH/token
Must set _buyFee = 1 (not 10¹⁸)
Actual fee: (1 × 10¹⁸) wei = 1 ETH` (works but contradicts standard wei practice)
Essential Safeguards:
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.
The contest is complete and the rewards are being distributed.