Enforce the rate limiter on submission entry points

[Meshmulla]

Summary

We have a rate_limiter module (soroban/src/rate_limiter.rs), but it doesn't appear to be enforced on the submission entry points. Wiring it in would protect against spam and abuse (e.g. a single operator flooding submissions) and make resource usage more predictable.

What we'd like

• Apply rate limiting to the submission / report entry points
• Make limits configurable (per-caller window and max count) by an admin role
• Reject over-limit calls with a clear, specific error

Where to look

• soroban/src/rate_limiter.rs — the limiter primitive
• soroban/src/submission_pause.rs, submission_replay.rs, report_hash.rs — submission-related flows to guard
• soroban/src/acl.rs — who can configure the limits

Acceptance criteria

• Submission entry points enforce the rate limiter
• Limits are admin-configurable (window + max)
• Over-limit calls revert with a descriptive error
• Tests cover under-limit success, over-limit rejection, and window reset

Notes

Be mindful of ledger storage costs per caller — document the storage footprint of the limiter state.

[zhero-o]

I would love to work on this issue. Can I get assigned?

[priscaenoch]

hello maintainer,

The rate limiter is already implemented, so the main task here is making it part of the actual submission flow rather than introducing another limiting mechanism. I'd trace the submission and report entry points, identify where caller identity is available, and enforce the limiter consistently before expensive state changes or processing occur.

I'd keep the limits admin-configurable through the existing ACL model, with separate window and maximum-call settings, and make the rejection path explicit with a dedicated error. The tests should cover normal submissions, repeated calls within the window, and successful submissions once the window resets, including verifying that configuration changes take effect correctly.

[grantfox-oss]

🦊 GrantFox — @priscaenoch has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.