[Docs] Create Smart Contract Event Reference Guide

[Abd-Standard]

Description

Develop a dedicated documentation page that explains all emitted smart contract events within NotifyChain. The guide should help contributors, integrators, and backend developers understand event purposes, parameters, and expected usage patterns.

Tasks
Document every emitted event.
Explain event parameters and data types.
Include practical event examples.
Add usage recommendations for indexers and listeners.

Acceptance Criteria
All contract events are documented.
Examples are accurate and easy to understand.
Documentation is linked from the main docs.

Contributors start work by running:

git checkout -b docs/event-reference-guide

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[Senorespecial]

I would love to work on this issue, please assign issue to me.

[nikkidev0984]

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

Hi maintainer. I am a 3rd year CS student and have active background as an open source contributor. I will be able to handle this issue efficiently please allow me to work on this.

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

[Darkdruce]

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

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

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

[drips-wave]

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

🧑‍💻 @Darkdruce: 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 — @Darkdruce 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 #274)
2. Your PR will be reviewed by the Core-Foundry maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

😎 @Darkdruce: You earned 200 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.