Implement Transaction History Display Optimization

[sssning121]

Expected Behavior

After a user submits a transaction, it should appear immediately in the transaction history list without waiting for on-chain confirmation. The transaction status should be updated dynamically to “Pending”, “Confirmed”, or “Failed”, improving user feedback and visibility.-chain data verification. At the same time, it should refactor the existing EVM contract event handling logic to improve stability and scalability.

Specifications

As a user, I would like to see my transaction appear in the history list immediately after submission,
so that I can confirm the system has accepted my action without waiting for on-chain confirmation.

Features:

• Implement immediate rendering of submitted transactions, regardless of confirmation state;
• Add a Status field to transaction records (e.g., Pending, Success, Failed);
• Enable backend service to listen to EVM events and update statuses asynchronously;
• Listen to confirmed limiter contract events to update limit-related data.

Development Tasks:

• Use WebSocket to listen to EVM chain events in real time;
• Add a Status field and related enum types to the transaction record entity;
• Implement background service or scheduled job for handling transaction confirmation and rollback logic;
• Extract core event handling logic to decouple responsibilities and improve testability;
• Update limit information upon detecting confirmed events from the limiter contract.