Beedle - Oracle free perpetual lending

Summary

The smart contract does not utilize events for significant state changes, reducing transparency and hindering debugging efforts.

Vulnerability Details

The contract does not emit events. Key operations such as deposit, withdraw, and claim are currently silent in terms of events.

Impact

1. Lack of real-time tracking of contract activities.

2. Increased difficulty in debugging issues.

3. Inability for interfaces to respond to state changes.

Tools Used

Manual Code Review

Recommendations

1. Implement custom events for essential functions, especially those that modify contract state.

2. Introduce events like Deposited(address indexed user, uint256 amount), Withdrawn(address indexed user, uint256 amount), and Claimed(address indexed user, uint256 amount) to improve transparency and interactivity.