[Contracts] Emit an event when update_fee_config changes treasury or fee rate

[ogazboiz]

Join the discussion on Telegram

Why this matters

update_fee_config (contracts/stream_contract/src/lib.rs) changes protocol-critical state — the treasury address and the fee rate that is applied to every create_stream and top_up_stream. Unlike every other mutating function in the contract, it emits no event. The off-chain indexer therefore has no way to observe or audit a fee/treasury change, and an admin dashboard cannot show fee-config history. For a protocol that collects fees from user funds, silent, unauditable fee changes are a transparency and trust problem.

Acceptance criteria

• Add a FeeConfigUpdatedEvent to contracts/stream_contract/src/events.rs carrying at least { admin, old_treasury, new_treasury, old_fee_rate_bps, new_fee_rate_bps }.
• Emit it from update_fee_config in contracts/stream_contract/src/lib.rs (and consider emitting an Initialized event from initialize for symmetry).
• Add a unit test in contracts/stream_contract/src/test.rs asserting the event is published with correct fields.
• Document the new event topic in any contract event documentation.

Files to touch

• contracts/stream_contract/src/events.rs
• contracts/stream_contract/src/lib.rs
• contracts/stream_contract/src/test.rs

Out of scope

• Indexing the new event in the backend worker (follow-up).

[LawalRahman]

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

I would like to work on this project please

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

[larryjay007]

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

Hi, I would like to work on this issue.

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

[drips-wave]

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

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

[drips-wave]

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

😎 @LawalRahman: 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.