Add Event Filtering Helpers in TypeScript Service

[Just-Bamford]

��# Issue 14: Add Event Filtering Helpers in TypeScript Service

Problem

TypeScript service can't efficiently filter contract events by type or ballot ID. Requires manual iteration.

Solution

• Add SorobanEventFilter interface: eventType, ballotIdHash, startTime, endTime
• Implement sorobanFilterEvents() helper to query and filter events
• Add SorobanEventData interface with parsed event fields
• Makes audit trail queries efficient for core services

Implementation Tasks

• Define SorobanEventFilter and SorobanEventData interfaces
• Implement sorobanFilterEvents(config, filter) helper
• Add event type parsing and filtering logic
• Handle time range queries (startTime, endTime)
• Unit tests: events filtered by type
• Unit tests: events filtered by ballot ID and time range

Note for Contributors

This is a TypeScript service layer feature independent of contract changes. Implement efficient event filtering to support audit queries from AnonVote/core. Query events from the Soroban RPC endpoint using the contract ID and event types. Parse event data into structured SorobanEventData objects. Support multiple filters: event type (e.g., "ballot_created", "token_issued"), ballot ID hash, and time ranges. Filtering is client-side after RPC query; optimize by querying only relevant events from RPC. Consider pagination for large event streams. Use consistent event naming with the contract's emitted events (see Issues #1, #4).

[Osuochasam]

Allow me to work on this issue, I will solve it

[k-deejah]

Hello Maintainer,

I would like to work on this issue. I have experience building TypeScript service layers and working with blockchain event data. I can implement the SorobanEventFilter and SorobanEventData interfaces, build the sorobanFilterEvents() helper with support for event type, ballot ID, and time-range filtering, and ensure event data is parsed into a clean, strongly typed structure. I will also add comprehensive unit tests covering the required filtering scenarios and consider efficient querying and pagination strategies for larger event streams while keeping the implementation aligned with the project's architecture.

Thank you for your consideration.

[grantfox-oss]

🦊 GrantFox — @k-deejah has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #32)
2. Your PR will be reviewed by the AnonVote maintainers

Good luck! Track your progress on GrantFox.