Implement rate limiting and DDoS protection - #53
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: Implement Rate Limiting & DDoS Protection for Contract Operations
Overview
This PR introduces configurable rate limiting and DDoS protection across contract operations to prevent abuse of registration, verification, and revocation workflows.
Previously, the contract had no active throttling mechanism despite an existing rate_limit.rs implementation. This allowed malicious actors to repeatedly invoke contract operations, potentially flooding ledger state, degrading indexer performance, and increasing operational costs.
What Changed
Observability & Metrics
Added rate limit telemetry and monitoring.
Tracks:
Testing
Added comprehensive test coverage for:
Burst allowance behavior
Token refill mechanics
Per-issuer throttling
Per-address throttling
Rate limit reset scenarios
Concurrent caller behavior
Error responses and retry-after handling
Files Updated
src/lib.rs
src/rate_limit.rs
src/config.rs
src/stellar.rs
src/metrics.rs
src/test.rs
Cargo.toml
README.md
Impact
This change significantly reduces the risk of contract abuse, ledger pollution, and denial-of-service attacks while providing configurable controls that can be tuned for legitimate high-volume issuers and production workloads.