Soroban event reference doc

[Asheeyah23]

Background

A reference of every event the indexer recognizes (transfer, mint, burn, approve) with example XDR.

What to build

A docs page listing each supported event with shape, source, decoded form.

Key files

• docs/event-reference.md (new)

Acceptance criteria

• One section per event
• Each with example

Drips Wave · Complexity: Intermediate · 150 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[Tundeakinbami-dev]

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

Hi maintainer, I would like to work on this issue. I can finish it in 20minutes.

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

[githoboman]

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

Hey, I'd like to take this on.

I've already cloned and read through the codebase for a related issue, so I have a solid foundation here. The event shapes are already fully documented in code — decoder.ts has the SEP-41 topic layouts for transfer, mint, burn, and clawback; ingester/nft.ts covers the CAP-46 4-topic NFT transfer; and host-fn-log.ts covers the raw host-fn path. The fixture XDR in src/__tests__/fixtures/events.json gives me real base64 examples to decode and include.

Planned structure for docs/event-reference.md:

• One section per event type: transfer, mint, burn, clawback, NFT transfer (4-topic), and host-fn log
• For each: topic layout table, decoded native form, example XDR pulled from the test fixtures, and any edge cases (e.g. mint fromAddress is null by design, burn has no toAddress)
• Note on how the indexer distinguishes NFT vs fungible transfers (topic count + value type)
• Cross-links to the relevant source files for maintainability

Clean, maintainer-friendly markdown. ETA 1–2 days.

Full-stack blockchain dev with active Web3 indexer experience on TypeScript/Soroban stacks. GitHub: githoboman

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

[drips-wave]

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

🧑‍💻 @githoboman: 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 🌊