Cross-crate symbol catalog — single source of truth for event topic names

[greatest0fallt1me]

Description

Event topic strings ("init", "pause_set", "distribute", "admin_changed") are repeated as ad-hoc Symbol::new(&env, "...") calls across the three crates. Extract a shared events module per crate that exports pub const Symbol topic constants so renames are mechanical and the catalog is grep-able.

Requirements and Context

• New contracts/<crate>/src/events.rs with pub fn event_init(env: &Env) -> Symbol (or similar) per topic
• Replace inline literals at emit sites
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/event-symbol-catalog

2. Implement changes
   • contracts/vault/src/events.rs, contracts/settlement/src/events.rs, contracts/revenue_pool/src/events.rs
   • Replace Symbol::new(&env, "init") etc. throughout
3. Test and commit
   • cargo test --workspace
   • Cover edge cases: every topic still produces identical bytes (snapshot test)
   • Include test output and notes in the PR

Example commit message

task: centralize event topic symbols per crate

Acceptance Criteria

• No remaining inline Symbol::new(env, "...") for event topics
• Topic-byte snapshot test prevents accidental renames
• EVENT_SCHEMA.md cross-links each topic constant

Guidelines

• .rs only under contracts/.../src/, NatSpec-style /// doc comments
• Use real Soroban SDK idioms
• Clear documentation and inline comments
• Timeframe: 96 hours

[zinodict121]

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

Hi maintainer, I will love to work on this issue. Please assign it to me

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

[drips-wave]

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

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