The MerkleAirdrop contract lacks an updateMerkleRoot
function, preventing the contract owner from updating the Merkle root after deployment.
Without an updateMerkleRoot
function, the contract becomes static once deployed, with no mechanism to modify the Merkle root or update the airdrop data. This limitation restricts the contract's adaptability and flexibility, potentially leading to various issues such as incorrect airdrop data, inability to adjust the airdrop list, and stranded funds.
Inability to update airdrop data: The contract owner cannot modify the airdrop list or correct errors in the Merkle tree data, leading to potential inaccuracies in token distribution.
Lack of adaptability: Market conditions or campaign requirements may change over time, but without the ability to update the Merkle root, the contract remains static and cannot be adjusted accordingly.
Risk of stranded funds: Any remaining tokens in the contract after the airdrop completion cannot be recovered or redistributed without a contract upgrade.
Manual review
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.