[Backend] Indexer ignores fee_config_updated and admin_transferred governance events

[ogazboiz]

Join the discussion on Telegram

Why this matters

The Soroban contract now emits two governance events that are never indexed:

• fee_config_updated -> FeeConfigUpdatedEvent (added for [Contracts] Emit an event when update_fee_config changes treasury or fee rate #458) — emitted from update_fee_config in contracts/stream_contract/src/lib.rs:108.
• admin_transferred -> AdminTransferredEvent (added for [Contracts] Add transfer_admin so protocol ownership can be rotated #459) — emitted from transfer_admin in contracts/stream_contract/src/lib.rs:151.

Both are emitted with a single-element topic ((Symbol,)), but SorobanEventWorker.processEvent bails out early for any event with fewer than 2 topics:

// backend/src/workers/soroban-event-worker.ts:250
if (!event.topic || event.topic.length < 2) return;

So these events are dropped before they ever reach the switch, and the switch has no case for them anyway (only the 8 stream-lifecycle events are handled). The result: a treasury/fee-rate change or an admin rotation produces no StreamEvent row, no SSE broadcast, and no audit trail in the backend, even though the chain recorded it. The event-type taxonomy (backend/src/routes/v1/events.routes.ts, stream.controller.ts validEventTypes, and the frontend EVENT_STYLES) also has no entries for these.

These are protocol-level governance actions; not surfacing them is a real observability/audit gap, and the events were just added to the contract this cycle.

Acceptance criteria

• Allow single-topic events through processEvent (handle topic.length === 1 for protocol events while still requiring streamId topic for per-stream events).
• Add a fee_config_updated handler that persists a FEE_CONFIG_UPDATED record (decode admin, old_treasury, new_treasury, old_fee_rate_bps, new_fee_rate_bps).
• Add an admin_transferred handler that persists an ADMIN_TRANSFERRED record (decode previous_admin, new_admin).
• Add the two new event-type strings to the allow-list in backend/src/routes/v1/events.routes.ts and validEventTypes in backend/src/controllers/stream.controller.ts.
• Broadcast the new events over SSE on a protocol/admin channel (these are not tied to a single streamId).
• Add worker unit/integration coverage asserting both event types are decoded and stored.

Files to touch

• backend/src/workers/soroban-event-worker.ts
• backend/src/routes/v1/events.routes.ts
• backend/src/controllers/stream.controller.ts
• backend/src/__tests__/integration/streams.test.ts

Out of scope

• Frontend rendering of governance events (a small follow-up to add EVENT_STYLES entries can be a separate issue).
• Changing the contract event shapes.

[Daveside9]

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

can i do this? merge in 2hours.

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

[chiscookeke11]

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

Please can I work on this task

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

[Rampop01]

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

I would like to work on this issue . I understand the assignment and the requirements, and I’m confident in the approach needed to deliver the best solution. Kindly assign this task to me.

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

[drips-wave]

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

🧑‍💻 @Rampop01: 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 @Rampop01 as part of the Stellar Wave Program's 5th Wave 🥳

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