Add helper for converting raw Stellar event fields to the server trade event schema

[Chucks1093]

Summary

The indexer receives raw Soroban event data from the Stellar RPC and must map it to the server's internal trade event schema. This mapping should live in a dedicated helper so it can be unit tested without invoking the RPC and reused across different event parsers.

Scope

• Add parseStellarTradeEvent(rawEvent): TradeEvent helper
• Maps raw Soroban event topic and data fields to: event_type, creator_id, actor_address, amount, price, fee, ledger_sequence, timestamp
• Throws a typed ParseError if any required field is missing or the wrong type
• Add unit tests for a valid buy event, a valid sell event, and a missing required field

Acceptance Criteria

• Valid buy event maps to correct schema fields
• Valid sell event maps to correct schema fields
• Missing required field throws ParseError
• No RPC calls made in tests

ETA: 12 hours

---

Coordinate on Telegram

[Danielobito009]

@Danielobito009 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i want to work on this issue, please assign me.

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

[Godfrey-Delight]

@Godfrey-Delight has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would love to work on this

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

[extolkom]

@extolkom has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Assign me pls

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

[ojuotimi932]

@ojuotimi932 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please assign

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

[drips-wave]

Congratulations, @Godfrey-Delight! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Godfrey-Delight: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @Godfrey-Delight 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 #513)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Godfrey-Delight's PR #526 was approved and merged by @Chucks1093.

🏆 @Godfrey-Delight: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (471 total points). Track your full progress on GrantFox.

👏 Great work, @Godfrey-Delight! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @Godfrey-Delight as part of the Stellar Wave Program's 6th Wave 🥳

😎 @Godfrey-Delight: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.