Implement Transaction History/Activity Endpoint

[KuchiMercy]

Complexity: Medium (150 points)

Description

Add dedicated endpoint to retrieve escrow activity history with filtering and pagination.

Requirements and Context

EscrowEvent entity logs all escrow actions but lacks dedicated retrieval endpoint
Events are returned nested in escrow response but no standalone query
Users need to audit escrow timeline for transparency and dispute evidence
Required for dashboard activity feeds

Suggested Execution

Fork repo, create branch feat/transaction-history
Create ListEventsDto with filters: eventType, dateRange, actorId
Add findEvents method to EscrowService
Create endpoints:
GET /escrows/:id/events - events for specific escrow
GET /events - all events for user's escrows (with pagination)
Support sorting by timestamp (default: descending)
Include actor details (wallet address) in response

Test and Commit

Test pagination and filtering
Test user can only see events from their escrows
Verify event ordering
Test empty result sets

Example Commit Message

feat: add escrow activity history endpoints with filtering

Expose escrow events via dedicated endpoints supporting pagination,
filtering by event type, and date range queries.

Guidelines

Ensure party-level access control (users see only their escrows' events)
Consider rate limiting for event queries
Format timestamps consistently (ISO 8601)
Support cursor-based pagination for performance (future enhancement)

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[licette32]

@licette32 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I’d like to apply for this issue.
I’ve reviewed the requirements and I have a clear understanding of the activity tracking logic needed.
If assigned, I’ll follow the project’s guidelines and keep communication clear during the process.
Thanks for your consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @licette32 to this issue.