Feat: Implemented High-Frequency Contract Calls detection#159
Open
Chongai-Cli wants to merge 1 commit into
Open
Feat: Implemented High-Frequency Contract Calls detection#159Chongai-Cli wants to merge 1 commit into
Chongai-Cli wants to merge 1 commit into
Conversation
Collaborator
|
Hello @Chongai-Cli , thank you for your contribution, please kindly fix the git workflow failures? Thanks for your usual cooperation, looking forward to work with you on this project for more issues |
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.
Description
Here's what was built:
4 files created, 1 modified:
apps/backend/src/modules/detection/contracts/
├── interfaces/
│ └── spike-detection.interface.ts ←
SpikeDetectionConfig, ContractActivityRecord,
SpikeAlert
├── spike-detection.service.ts ← core
logic
├── spike-detection.module.ts ← NestJS
module
└── spike-detection.service.spec.ts ← 13 unit
tests
apps/backend/src/app.module.ts ←
SpikeDetectionModule registered
How it works:
The service uses a dual rolling window for baseline
comparison — a "current" window and an equally-sized
"previous" window:
|← baseline window →|← current window →|
now - 2×windowMs now - windowMs now
When recordTransaction(address, timestamp) is
called, it compares the current window count against
the baseline:
(suppresses noise during cold start)
(default 3×) → no alert
SpikeAlert
Type of Change
Related Issues
Fixes #150
Related to #
Changes Made
Testing
npm run test)npm run lint)npm run format)npm run build)Checklist
Screenshots (if applicable)
Additional Context