Add helper for generating a unique idempotency key from request body hash

[Chucks1093]

Summary

Mutation endpoints like alert registration and webhook registration should be idempotent when the same request is submitted twice. A shared helper that hashes the request body and returns a stable idempotency key allows duplicate detection without requiring clients to send an explicit key.

Scope

• Add hashRequestBody(body: unknown): string helper using a stable hash function (e.g. SHA-256)
• Returns a hex string of fixed length
• Same input always produces the same output
• Add unit tests for: identical objects produce identical hashes, different objects produce different hashes, empty object has a stable hash

Acceptance Criteria

• Identical input always produces the same hash
• Different inputs produce different hashes
• Output is a fixed-length hex string
• Empty object produces a valid hash without throwing

ETA: 12 hours

---

Coordinate on Telegram

[Luchistack]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[Kappa16]

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

Please maintainer..I can handle this professionally and make sure this issue is closed ASAP WITHOUT ERRORS.

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

[dubemoyibe-star]

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

Can I work on this issue

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

[ojuotimi932]

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

Please assign

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

[extolkom]

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

Please assign me

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @dubemoyibe-star has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #517)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@dubemoyibe-star's PR #523 was approved and merged by @Chucks1093.

🏆 @dubemoyibe-star: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (521 total points). Track your full progress on GrantFox.

👏 Great work, @dubemoyibe-star! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @dubemoyibe-star as part of the Stellar Wave Program's 6th Wave 🥳

😎 @dubemoyibe-star: You earned 150 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.