Submission Details
Severity:
Lack of Reentrancy Protection
Description: No explicit reentrancy guards in critical transfer and state-changing functions.
In ITransmuter:
deposit(),claim(),withdraw()potentially vulnerableNo use of checks-effects-interactions pattern
No reentrancy guard modifier
Impact:
Potential drain of contract funds
State manipulation
Economic loss
Proof of Concept:
contract ReentrancyAttack {
ITransmuter transmuter;
function attack() external {
transmuter.claim(attackAmount, address(this));
}
// Malicious fallback function
receive() external payable {
transmuter.claim(attackAmount, address(this));
}
}
Recommended Mitigation:
Implement ReentrancyGuard from OpenZeppelin
Use checks-effects-interactions pattern
Add explicit reentrancy checks
Prize pool breakdown
Total prize
16,653 OP
nSLOC
25366 OP / LOC
15,800
853
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.