40,000 USDC
View results
Submission Details
Severity: low

Emits Events Last

Summary

Emitting events at the end of the function execution

Vulnerability Details

In general, it is best practice to emit events after all state changes and token transfers are completed. This ensures that events are only emitted if the transaction has been successfully executed, preventing inconsistent event logs in case of reverted transactions.

Impact

function resolveDispute(uint256 buyerAward) external onlyArbiter nonReentrant inState(State.Disputed) {
uint256 tokenBalance = i_tokenContract.balanceOf(address(this));
uint256 totalFee = buyerAward + i_arbiterFee; // Reverts on overflow
if (totalFee > tokenBalance) {
revert Escrow__TotalFeeExceedsBalance(tokenBalance, totalFee);
}
s_state = State.Resolved;
emit Resolved(i_buyer, i_seller);
if (buyerAward > 0) {
i_tokenContract.safeTransfer(i_buyer, buyerAward);
}
if (i_arbiterFee > 0) {
i_tokenContract.safeTransfer(i_arbiter, i_arbiterFee);
}
tokenBalance = i_tokenContract.balanceOf(address(this));
if (tokenBalance > 0) {
i_tokenContract.safeTransfer(i_seller, tokenBalance);
}
}
function confirmReceipt() external onlyBuyer inState(State.Created) {
s_state = State.Confirmed;
emit Confirmed(i_seller);
i_tokenContract.safeTransfer(i_seller, i_tokenContract.balanceOf(address(this)));
}

Tools Used

Manual Review

Recommendations

emit events after all state changes and token transfers are completed

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.