Implement Stellar v2 announcer event topic schema with indexed view-tag bucket

[David-patrick-chuks]

Follow-up to #23.

Implement the recommended v2 Stellar stealth-announcer event schema:

• topics: ("announce", scheme_id, view_tag_bucket, metadata_kind)
• data: (stealth_address, ephemeral_pub_key, metadata)

Scope:

• add the new event layout in stellar/stealth-announcer
• define a stable view_tag_bucket derivation rule
• define the initial metadata_kind convention
• update tests/snapshots for the new topic layout
• document the v1 -> v2 migration expectations in code comments or contract docs

Compatibility:

• use the v2 rollout path recommended in Soroban event topic strategy: indexed topics for efficient scan filtering #23: new deployment + scheme_id = 2
• do not silently mutate historical v1 semantics

Success means wallets/indexers can filter Stellar RPC getEvents by scheme and bucket before client-side cryptographic validation.

[1sraeliteX]

@1sraeliteX 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

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

[Kappa16]

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

please maintainer... assign this issue to me ... ill resolve this issue without errors ASAP

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

[blurbeast]

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

hello my Boss , can i jump on this ??

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

[Emmanuel-abiola]

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

Hi, I’d like to work on this issue. I will implement the Stellar v2 stealth-announcer event schema by updating the event structure in stellar/stealth-announcer to match the new topic format.

I’ll define a stable view_tag_bucket derivation rule and introduce a clear metadata_kind convention for consistent event categorization. I’ll also update existing tests and snapshots to reflect the new topic layout and ensure backward compatibility expectations are clearly validated.

Additionally, I’ll document the v1 → v2 migration behavior in the contract or relevant module comments to make the transition clear for downstream consumers.

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

[gloskull]

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

Hello,

I’m a developer with 4 years of hands-on experience working on production-grade systems and contributing to collaborative, open-source environments. I’ve carefully read through this issue and fully understand the problem it addresses, the expected outcomes, and the constraints outlined in the acceptance criteria.

I’m comfortable taking ownership from start to finish: reviewing the existing codebase and related context, designing a clean and maintainable solution, implementing it with attention to edge cases and correctness, and validating everything with appropriate tests and documentation where required. I place strong emphasis on clarity, reliability, and aligning closely with the project’s existing patterns and standards, so the final result is easy to review and integrate.

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

[Malcolm-Wander]

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

Hello maintainer,I’d love to work on this issue please…thank you

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

[drips-wave]

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

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