[Wave 9] Add deterministic event identity and cross-chunk deduplication

[truthixify]

Problem

Parallel scans deduplicate with provider event IDs or a serialized topic fallback. The identity contract is not public, so different providers can produce duplicates across pages or chunks.

Done when

• Define a stable event identity from chain, transaction, event index, and contract data.
• Use it consistently in sequential and parallel scans.
• Expose enough metadata for callers to persist deduplication state.
• Add duplicate and provider-variation fixtures.

[victorocheje]

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

I would like to work on this issue

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

[Simbabi]

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

I’d like to take this on by defining a stable event identity from the chain, transaction, event index, and contract data, then using it consistently across sequential and parallel scans. I’ll also add fixtures covering duplicate events and provider-specific variations, while exposing the metadata needed for callers to persist deduplication state.

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

[SixtusEzeogu]

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

Hello, I’d like to contribute to this issue and would appreciate the opportunity to work on it. Thank you for considering my request.

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

[Xhaka00]

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

I’m interested in the available opportunity. I may be seeking a chance to prove myself, but I’m ready to work hard, learn fast, and contribute positively. I look forward to your consideration.

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

[Immaculate0606]

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

Please kindly assign. I can fix this

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

[Princejay04]

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

Hello Maintainer, this issue aligns well with my technical experience, and I’m confident I can analyze the underlying problem, implement a robust solution that adheres to the existing architecture and requirements, and validate the changes with appropriate testing. I’d appreciate the opportunity to take ownership of this issue and submit a well-tested pull request.

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

[Folarin-Olamide]

@Folarin-Olamide has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

hello maintainer, i will love to work on this issue, kindly assign it to me

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

[Adeyemiadigun]

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

Hello Maintainer,
I've reviewed the requirements for deterministic event identity and cross-chunk deduplication and am confident I can deliver a clean, efficient solution. Please assign this issue to me.

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

[Nemenwa]

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

Hi, I’d like to work on this issue. I’ve reviewed the requirements and would be happy to take it on. Please assign it to me. Thank you!

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

[philipeh]

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

Hello Maintainer, I’ve taken some time to review this issue and understand the work involved. I’d be happy to take responsibility for resolving it and delivering a solution that meets the requirements.

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

[code3ks]

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

Hi maintainer,i would be glad to work on this issue if assigned.

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

[manlikesilva]

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

Hello, I’ve reviewed the issue description and have a clear understanding of what’s required. I’d be excited to take on the task and confident in my ability to approach it effectively and deliver a solid result.

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

[drips-wave]

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

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